TypeScript, end-to-end.
One language across frontend and backend, strict mode on. React or vanilla DOM on the surface; Node.js or Bun behind it; Drizzle or Prisma over PostgreSQL; tRPC or REST, depending on the team.
THE RECORD — THE STACK
What runs underneath.
A modern, owned stack — TypeScript end-to-end, PostgreSQL, cloud-portable — chosen for ten-year durability, not the trend cycle.
Everything on this page is a default, not a hard requirement: source you hold, infrastructure you own, components replaceable without a rewrite. Written for the engineer your company asks to check our work.
LANGUAGE TYPESCRIPTDATABASE POSTGRESQLDEPLOY CLOUD-PORTABLELOCK-IN — NONE
02 — THE LAYERS
Three layers, one source of truth.
Application, infrastructure, and the ledger that makes every action queryable. Each layer is owned outright; none of it is rented.
Cloud-portable, owned.
Deployable to AWS, GCP, Vercel, or your own VPC. Terraform or Pulumi for infrastructure as code, GitHub Actions for CI/CD, and Sentry, Grafana, and OpenTelemetry watching every hop.
The ledger, underneath it all.
Every state-changing action lands in an append-only event record beside the data it changed. Read how it works — it is the part your auditors thank you for.
03 — THE LIVING LEDGER
Every action, on the record.
The Living Ledger is the shop's standing architecture rule: every action an event, every event auditable, every audit one query away.
STANDING RULE — EVERY BUILD, EVERY BAND
Audit is a query, not a project.
Every state-changing action is written as an event — idempotent, signed, persisted in PostgreSQL beside the data it changed. Who did what, when, to which record: one SQL query. Compliance reviews, customer disputes, debugging at 2 a.m. — all read from the same strip.
EVERY WRITE → EVENTAUDIT — ONE QUERY
See the commitments04 — THE TOPOLOGY
How the layers connect.
Every Toledo build follows the same drawing: the browser talks to a stateless API; the API writes to PostgreSQL and appends to the ledger; observability watches every hop.
DRAWN ONCE, SHIPPED ANYWHERE
Different floor, same build.
Cloud-portable means every box in the drawing can change providers without a rewrite. The same source ships to Vercel, AWS, GCP, DigitalOcean, or your own VPC — containers and Terraform underneath, so the floor is an implementation detail, not a marriage.
STATELESS APISCALES HORIZONTALLY
See the four lanes05 — DEFAULTS
Defaults, not dogma.
Every component below is portable, owned, and replaceable. None are hard requirements; all are defaults that have to earn their seat on each build.
-
01
UI
Frontend
React · TypeScript · Tailwind · Vite — or vanilla DOM where the work calls for it.
-
02
API
Backend
Node.js · Bun · tRPC · REST · Hono · Express, depending on the team's read.
-
03
DATA
Database
PostgreSQL · Drizzle ORM · Prisma · raw SQL where it earns its keep.
-
04
DEPLOY
Hosting
AWS · GCP · Vercel · your own VPC — containerized so the floor stays portable.
-
05
OPS
IaC & CI
Terraform · Pulumi · GitHub Actions for CI/CD — the infrastructure is in writing too.
-
06
AUDIT
Observability
Sentry · Grafana · OpenTelemetry — structured logs, every event a row.
06 — BEGIN
Run it past your engineers.
This page is written to be forwarded. If your technical advisor has questions it doesn't answer, the principal answers them directly — before any money moves.
DELPHI APP DISCOVERY MOST COMMON
For internal tools, portals, and custom apps.
A short engagement to scope the build before you commit to it — and the stack above, pinned in writing to your particular system.
- Two scoping workshops with the principal
- Written architecture brief and data model
- Fixed-band quote you can hold us to
$3,500–$5,000 · 1–2 WEEKS
Begin
TECHNICAL QUESTIONS FIRST
Email the principal.
Forward this page with three sentences about the operation. The reply comes within one business day — from the person who would design and build the system.
CREDIT RULE — 50% OF THE DISCOVERY FEE CREDITS TOWARD YOUR KICKOFF PROJECT RETAINER WITHIN 30 DAYS.