# Grayhat Tech Radar

> Public Grayhat Tech Radar page rendered from build-time generated static assets.

## Page

- [Tech Radar](https://grayhat.studio/tech-radar)
- [Root LLM Context](https://grayhat.studio/llms.txt)
- [Tech Radar Full LLM Context](https://grayhat.studio/tech-radar/llms-full.txt)
- [Sitemap](https://grayhat.studio/sitemap.xml)


## Header

### Company Information

- Company: Grayhat Developers PVT Ltd
- Brand: Grayhat
- Base URL: https://grayhat.studio
- Tagline: We build cool stuff
- Description: Grayhat develops technology solutions for clients around the world, ranging from startup apps to full-fledged existing systems.
- Vision: We aim to make a significant impact in future tech, and build solutions which can be used by the people around us.
- Established: 2022
- Service areas: Global

### Primary Navigation

- [Home](https://grayhat.studio/)
- [Careers](https://grayhat.studio/careers)
- [Team](https://grayhat.studio/team)
- [Projects](https://grayhat.studio/projects)
- [Clients](https://grayhat.studio/clients)
- [Research](https://grayhat.studio/research)
- [Blog](https://grayhat.studio/blog)
- [About](https://grayhat.studio/about)

### Social Links

- [LinkedIn](https://www.linkedin.com/company/76504684)
- [GitHub](https://github.com/grayhatdevelopers)
- [Dribbble](https://dribbble.com/grayhatstudio)
- [Discord](https://grayhat.studio/discord)
- [Instagram](https://www.instagram.com/grayhatdevelopers)
- [Facebook](https://www.facebook.com/grayhatdevelopers)

## Public Page Details

- Renders a same-origin static Tech Radar generated at build time with @qiwi/tech-radar.
- Technology Radar entries are authored in the typed radar catalogue and generated into package-rendered English and Simplified Chinese radar outputs.
- Each entry includes a ring, quadrant, description, use cases, and grounded Grayhat project associations where available.

## Page Content

- Purpose: An overview of the languages, frameworks, platforms, tools, and engineering practices we use across web applications, enterprise systems, artificial intelligence products, games, and cloud infrastructure.
- Canonical page: https://grayhat.studio/tech-radar
- Generated package output: https://grayhat.studio/generated/tech-radar/en/2026-07-23/index.html
- Technology count: 58
- Rings: Adopt, Trial, Assess, Hold
- Quadrants: Languages and Frameworks, Platforms and Infrastructure, Tools and Services, Techniques and Architecture

- **React.js** (Adopt; Languages and Frameworks): Used for production web interfaces and interactive product experiences.
- **Next.js** (Adopt; Languages and Frameworks): Used to build production websites, SaaS applications, and server-rendered platforms.
- **Node.js** (Adopt; Languages and Frameworks): Used for server-side JavaScript services, build tooling, and integration layers.
- **TypeScript** (Adopt; Languages and Frameworks): Used across strongly typed frontend, backend, worker, and tooling code.
- **JavaScript** (Adopt; Languages and Frameworks): Used where the web platform or third-party packages require plain JavaScript.
- **Python** (Trial; Languages and Frameworks): Used for AI, data, automation, and service prototypes where Python libraries are strongest.
- **FastAPI** (Assess; Languages and Frameworks): Considered for Python API services when typed request handling and async support matter.
- **Express.js** (Trial; Languages and Frameworks): Used selectively for Node HTTP services when a minimal server framework is enough.
- **React Native** (Assess; Languages and Frameworks): Evaluated for cross-platform mobile applications when one codebase is preferred.
- **Unity** (Trial; Languages and Frameworks): Used for game and interactive 3D work when a mature engine is a better fit than web rendering.
- **Java** (Assess; Languages and Frameworks): Kept under evaluation for enterprise and Android contexts when project needs justify it.
- **C#** (Trial; Languages and Frameworks): Used with Unity and game-facing systems where the engine ecosystem requires it.
- **Three.js** (Trial; Languages and Frameworks): Used for web-based 3D scenes and interactive visual experiences.
- **WebGL** (Trial; Languages and Frameworks): Used through higher-level rendering tools for graphics-heavy web experiences.
- **Tailwind CSS** (Adopt; Languages and Frameworks): Used for fast, token-aware interface styling in public and product surfaces.
- **Radix UI** (Adopt; Languages and Frameworks): Used as accessible primitives for tabs, dialogs, slots, and composable interface controls.
- **AWS** (Trial; Platforms and Infrastructure): Used selectively for cloud infrastructure when project requirements call for AWS services.
- **Vercel** (Trial; Platforms and Infrastructure): Used for Next.js application hosting where Vercel's workflow is the right operational fit.
- **Cloudflare** (Adopt; Platforms and Infrastructure): Used for public web delivery, edge routing, Workers, Pages, and managed platform primitives.
- **Cloudflare Workers** (Adopt; Platforms and Infrastructure): Used for edge runtime services, API surfaces, and OpenNext deployment targets.
- **Cloudflare Pages** (Trial; Platforms and Infrastructure): Used where static or framework-backed public surfaces fit the Pages model.
- **Docker** (Adopt; Platforms and Infrastructure): Used for local parity and services that are operated as containerized Node runtimes.
- **Kubernetes** (Assess; Platforms and Infrastructure): Evaluated only when orchestration needs exceed simpler platform primitives.
- **GitHub Actions** (Adopt; Platforms and Infrastructure): Used for CI, checks, and repeatable validation around repository changes.
- **Linux** (Adopt; Platforms and Infrastructure): Used as the base operating environment for servers, containers, and deployment tooling.
- **PostgreSQL** (Trial; Platforms and Infrastructure): Used or selected for relational product data when transactional integrity matters.
- **MongoDB** (Assess; Platforms and Infrastructure): Considered for document-shaped product data when the project evidence is specific enough.
- **Redis** (Trial; Platforms and Infrastructure): Used for queues, caching, and fast coordination in service runtimes.
- **Amazon S3** (Trial; Platforms and Infrastructure): Used as an object-storage pattern and compatible target for public and private assets.
- **MinIO** (Trial; Platforms and Infrastructure): Used for S3-compatible local and self-hosted object storage workflows.
- **Firebase** (Assess; Platforms and Infrastructure): Evaluated for app prototypes when managed auth, realtime, or hosting features fit.
- **Frappe** (Adopt; Tools and Services): Used as an operational source for ERP-backed content, jobs, clients, projects, and webhook flows.
- **ERP systems** (Adopt; Tools and Services): Used for business workflow integrations and public content projection from operational systems.
- **PlayroomKit** (Trial; Tools and Services): Used in the game portfolio for multiplayer and browser-native game experiences.
- **OpenAI APIs** (Trial; Tools and Services): Used for AI-assisted products, agents, content workflows, and research prototypes.
- **PyTorch** (Assess; Tools and Services): Evaluated for model work where deep learning experimentation is required.
- **Transformers** (Assess; Tools and Services): Evaluated for language and vision model workflows when model-level control is needed.
- **WebSockets** (Trial; Tools and Services): Used for realtime product and game interactions when persistent browser connections are needed.
- **Socket.IO** (Trial; Tools and Services): Used selectively where Socket.IO's fallback and event model simplify realtime delivery.
- **WebRTC** (Assess; Tools and Services): Evaluated for peer-to-peer media and low-latency collaborative experiences.
- **Playwright** (Adopt; Tools and Services): Used for browser validation, screenshots, accessibility checks, and end-to-end confidence.
- **GitHub** (Adopt; Tools and Services): Used for source control, pull requests, review workflows, and public repository surfaces.
- **Figma** (Adopt; Tools and Services): Used for product design, handoff, design review, and interface iteration.
- **Server-side rendering** (Adopt; Techniques and Architecture): Used for public pages and product surfaces that need crawlable, fast initial content.
- **Static-site generation** (Adopt; Techniques and Architecture): Used for stable public content, discovery files, and pages that benefit from build-time output.
- **Incremental static regeneration** (Trial; Techniques and Architecture): Used selectively when static pages need periodic refresh without full redeploys.
- **Microservices** (Trial; Techniques and Architecture): Used when service boundaries map cleanly to independently operated product capabilities.
- **REST APIs** (Adopt; Techniques and Architecture): Used for public and internal service contracts that need predictable HTTP semantics.
- **Event-driven architecture** (Trial; Techniques and Architecture): Used for webhook ingestion, queue-backed sync, fanout, and revalidation workflows.
- **Serverless architecture** (Adopt; Techniques and Architecture): Used where managed edge or serverless primitives reduce operational overhead.
- **Real-time multiplayer** (Trial; Techniques and Architecture): Used in game and collaboration contexts where shared live state is central.
- **AI agents** (Trial; Techniques and Architecture): Used in research and product workflows where autonomous assistance can improve delivery.
- **Retrieval-augmented generation** (Assess; Techniques and Architecture): Evaluated for AI products that need grounded answers over project or domain content.
- **Computer vision** (Assess; Techniques and Architecture): Evaluated for visual understanding, media analysis, and prototype intelligence features.
- **Responsive web design** (Adopt; Techniques and Architecture): Used across public and product work to support desktop, tablet, and mobile layouts.
- **CI/CD** (Adopt; Techniques and Architecture): Used to keep linting, type checking, tests, and deployments repeatable.
- **Containerization** (Adopt; Techniques and Architecture): Used for services where packaged runtime parity matters across local and production environments.
- **ERP integration** (Adopt; Techniques and Architecture): Used to connect operational business systems with public content and internal workflows.

## Related Public Pages

- [Home](https://grayhat.studio/)
- [About](https://grayhat.studio/about)
- [Privacy Policy](https://grayhat.studio/privacy-policy)
- [Terms and Conditions](https://grayhat.studio/terms-and-conditions)
- [Careers](https://grayhat.studio/careers)
- [Team](https://grayhat.studio/team)
- [Projects](https://grayhat.studio/projects)
- [Clients](https://grayhat.studio/clients)
- [Blog](https://grayhat.studio/blog)
- [Research](https://grayhat.studio/research)
- [Sitemap](https://grayhat.studio/sitemap)

## Current Snapshot

- 58 technology entrys across four rings and four quadrants.


## Footer

### Contact

- [info@grayhat.studio](mailto:info@grayhat.studio?subject=[grayhat.com.pk])
- [24, Street 3, Sector F DHA-2, Islamabad, Pakistan](https://maps.app.goo.gl/8gk8pTmDQxRaRPn49)

### Important Pages

- [Home](https://grayhat.studio/)
- [Careers](https://grayhat.studio/careers)
- [Team](https://grayhat.studio/team)
- [Projects](https://grayhat.studio/projects)
- [Clients](https://grayhat.studio/clients)
- [Research](https://grayhat.studio/research)
- [Blog](https://grayhat.studio/blog)
- [About](https://grayhat.studio/about)

### Legal Links

- [Privacy Policy](https://grayhat.studio/privacy-policy)
- [Terms and Conditions](https://grayhat.studio/terms-and-conditions)
- [Sitemap](https://grayhat.studio/sitemap)

### Third-party Platforms

- [Clutch](https://clutch.co/profile/grayhat)
- [Upwork](https://www.upwork.com/agencies/1539292796322222080/)
- [Glassdoor](https://www.glassdoor.com/Location/All-Grayhat-Developers-Islamabad-IS-Office-Locations-EI_IE8570949.4,22_IL.23,35_IC3139539.htm)

### Social Media

- [Instagram](https://www.instagram.com/grayhatdevelopers)
- [Facebook](https://www.facebook.com/grayhatdevelopers)

### Footer Metadata

- Tagline alt: We make 💻, ☕, and 🦄s
- Made in: Pakistan
- Copyright marker: Established in 2022
- [Legacy](https://grayhat.studio/who)