TECHNOLOGY

The stack, and why we chose it.

A logo grid proves nothing. Here is what we build with by default, what we choose it for, and where the decision is still open.

Items marked PENDING APPROVAL are decisions the senior team has not signed off yet. We would rather show the gap than pretend it is closed.

FRONTEND & PRODUCT

Next.jsReactTypeScriptTailwind CSSshadcn/uiFramer MotionLucide

Server rendering for speed and SEO, a typed codebase another team can inherit, and motion that is measured in milliseconds rather than decoration.

BACKEND & DATA

Node.jsREST & typed APIsPostgreSQLORM — PENDING APPROVAL

Relational data by default, because most business problems are relational. Authentication and payments use managed providers rather than hand-rolled code.

MOBILE

Cross-platform firstNative when justifiedFRAMEWORK — PENDING APPROVAL

We do not promise separate native iOS and Android builds when a cross-platform product is what the budget and the plan support.

INTELLIGENCE & AUTOMATION

LLM APIsRetrieval over your documentsWorkflow automationHuman approval & logging

Every automation is designed to stop at the decision. We do not call a chatbot an agent, and we do not ship full autonomy.

CLOUD, DEVOPS & SECURITY

CI on every changeStaging + rollbackSecrets managementMonitoring & backupsHOST — PENDING APPROVAL

Nobody deploys production from a laptop. Accounts are company-controlled and handed to you — never owned personally by a developer.

QUALITY & DESIGN

Acceptance criteriaAutomated testsSenior code reviewWCAG AA targetDesign system per client

Quality is a process, not a promise. Testing, documentation and review are scheduled work with named owners.