OOrveth

Documentation

Limitations

Honest scope boundaries for Orveth Phase 1 — what we do and do not provide.

Orveth Phase 1 is a stronger backend foundation, not a finished platform. Understanding limitations upfront helps you choose the right tools and set realistic expectations.

Not included in core

  • WebSockets — use a dedicated library or integration alongside Orveth
  • Full authentication platform — JWT helpers sign and verify tokens only
  • ORM or database layer — use Prisma, Drizzle, or your client of choice
  • Hosted deployment or managed cloud — you bring your own infrastructure
  • GraphQL or tRPC servers — HTTP routing is the core focus

Package scope

  • @orveth/cors and @orveth/security provide practical defaults, not enterprise policy engines
  • @orveth/validation-zod is the official Zod adapter — other schema libraries need custom middleware
  • @orveth/prisma adds health routes and shutdown hooks — Prisma remains Prisma

Maturity

We do not claim enterprise adoption, battle-tested production maturity, or benchmark leadership. Phase 1 is about foundation quality, package boundaries, and developer experience — documented honestly.