Architecture Overview

VeloxTS is designed to be flexible. You choose the architecture that fits your needs.

The Core Abstraction: Procedures

At the heart of VeloxTS is the procedure - a type-safe function that can be exposed as both tRPC and REST:

const getUser = procedure()
  .input(z.object({ id: z.string() }))
  .output(UserSchema)
  .query(async ({ input, ctx }) => {
    return ctx.db.user.findUniqueOrThrow({ where: { id: input.id } });
  });

This single definition generates:

• tRPC endpoint - Full type inference for TypeScript clients
• REST endpoint - GET /api/users/:id for any HTTP client

Architectural Patterns

1. REST API

External-facing API with automatic OpenAPI generation.

Client (any) → REST → VeloxTS → Database

Learn more

2. tRPC API

Maximum type safety for TypeScript clients.

TypeScript Client → tRPC → VeloxTS → Database

Learn more

3. SPA + Backend

Separate frontend, type-safe communication.

React SPA → tRPC Client → VeloxTS API → Database

Learn more

4. Full-stack RSC

Unified codebase with React Server Components.

Browser → Vinxi → RSC → Server Actions → VeloxTS → Database

Learn more

5. Hybrid

Combine patterns - tRPC for internal, REST for external.

Mobile App → REST ↘
                    VeloxTS → Database
Web App → tRPC   ↗

Learn more

Technology Stack

Layer	Technology
HTTP Server	Fastify
RPC	tRPC
Validation	Zod
ORM	Prisma
Full-stack	Vinxi + React 19

Next Steps

Choose your architecture:

• REST API - External clients
• tRPC API - TypeScript clients
• SPA + Backend - Separate frontend
• Full-stack RSC - Unified codebase