What services does A Major offer?

A Major offers web design, web app development, mobile app development (React Native, Swift, Flutter), SaaS product development, enterprise systems, UI/UX design, DevOps, performance optimization, MCP server development, AI agent infrastructure, MVP scoping, digital transformation, and engineering consultancy.

Where is A Major based?

A Major is based in Singapore and works with clients worldwide.

Do you work with international clients?

Yes. While headquartered in Singapore, A Major works with founders and businesses across Southeast Asia, Europe, and North America.

Ryu is an AI agent orchestration layer built by A Major. It enables teams to run, coordinate, and monitor AI agents at scale — connecting LLMs, tools, and workflows into reliable production systems.

Do you build MCP servers?

Yes. A Major builds Model Context Protocol (MCP) servers that connect AI agents to databases, APIs, and internal tools, enabling reliable LLM-powered workflows in production environments.

Can I use Prisma on Cloudflare Workers?

Yes, via Prisma Accelerate — a connection proxy that sits between Workers and your database. It adds latency and cost compared to Drizzle's native edge support. For edge-first architectures, Drizzle is simpler.

Which ORM works better with Supabase?

Both work with Supabase's Postgres database. Drizzle is popular in the Supabase community for its edge compatibility and smaller footprint. Prisma works too but requires connection pooling via Supabase's pgBouncer.

Is there a migration path between the two?

You can migrate by rewriting your schema definition and query calls. It's manual but not overwhelming for most codebases. We've helped teams switch both directions depending on infrastructure requirements.

What about TypeORM or Sequelize?

TypeORM and Sequelize are older ORMs with weaker TypeScript support. Both are being phased out in new projects in favour of Prisma or Drizzle. We wouldn't start a new project on either.

Prisma vs Drizzle ComparisonSchema-first abstractions vs SQL-close type safety — the TypeScript ORM debate

The ORM landscape shifted dramatically when Drizzle launched with a SQL-close API that avoided Prisma's runtime overhead. Prisma is mature, has excellent migrations, and is the most ergonomic ORM for developers who don't want to think about SQL. Drizzle is leaner, runs at the edge, and gives you more control over query execution. Both are production-ready. The choice largely comes down to how much SQL you want to write and whether you need edge runtime support.

Head-to-head summary

Prisma wins

Ties

Drizzle wins

Detailed comparison

API ergonomics

Prisma

Excellent — fluent, readable query API that non-SQL developers love

Drizzle

SQL-close — feels like writing SQL in TypeScript, suits SQL-comfortable devs

Bundle size

Prisma

Large — Prisma client is ~3MB, generated code is substantial

Drizzle

Tiny — Drizzle is ~7kb, designed for edge deployments

Edge runtime support

Prisma

Limited — Prisma Accelerate needed for edge; complex setup

Drizzle

Native — runs on Cloudflare Workers, Vercel Edge, Deno without adapters

Migrations

Prisma

Excellent — prisma migrate dev is intuitive and battle-tested

Drizzle

Good — drizzle-kit handles migrations, slightly more manual

Type safety

Prisma

Excellent — generated types are precise and IDE-friendly

Drizzle

Excellent — inferred types directly from schema definitions

Raw SQL escape hatch

Prisma

Available via prisma.$queryRaw — awkward to use

Drizzle

Natural — SQL syntax is the primary API, not an escape hatch

Ecosystem maturity

Prisma

More mature — larger community, more StackOverflow answers, older

Drizzle

Newer but growing fast — excellent documentation, active development

Our verdict

It's a tie — context determines the winner

Choose Prisma if you value its ergonomic API, rich documentation, and mature migration workflow. Choose Drizzle if you need edge runtime support, want a smaller bundle, or prefer SQL-close queries. Both are excellent — the decision is mostly about API style preference and infrastructure constraints.

When to choose each

Choose Prisma when:

Your team isn't SQL-fluent and wants an abstraction that hides query complexity
You're building a standard Node.js / Next.js app that doesn't need edge deployment
You value mature, battle-tested migrations and a large community
You need Prisma Studio — the visual database browser is genuinely useful

Choose Drizzle when:

You're deploying to Cloudflare Workers, Vercel Edge, or another edge runtime
Bundle size matters — serverless cold starts, or bundling a database client into a CLI
You're comfortable with SQL and want your queries to look like SQL
You need maximum query performance — Drizzle has less abstraction overhead