Serious products
at startup speed.
A complete backend for B2B, B2C and IoT products. Identity, events, real time, files, audit and operations are already built and running in production. Your team writes only its own domain.
Tequila in eight episodes
The platform as a founder meets it, about two minutes an episode: why Tequila, the first weeks, the auditor’s visit, a developer’s week, who is who, upgrade day, and the one file that decides it all.
Episode 1
Meet a founder with a serious product in mind. Serious means customers, their data, their money, and a regulator somewhere behind them. The usual way: hire developers, bolt on audit, event sourcing and access control one by one, and grow a crowd to maintain it. The Tequila way: one platform with one vision, so a small team ships a product that is enterprise-grade by construction, at startup speed and startup cost.
Episode 2
Last time, the founder chose Tequila. Now watch the first weeks: an empty organisation on GitHub, the whole estate on every developer's machine, a service from the template, a release cut by a merged pull request, and a deploy that is a pull request too — with its rendered diff, applied by Flux, rolled back by a revert.
Episode 3
The auditor from episode one comes for real. Compliance asks three things: show me what happened, prove nobody changed it, tell me what you cannot show. Here the answer is an invitation with one read-only role, a hash-linked audit trail with a verified copy of every service's log, a daily digest anchored in Sigstore Rekor and Bitcoin, an evidence pack that states its own caveats, and a person's export and erasure answered into the same trail. Two shots in the film are the real admin area of tequila.dev's own estate.
Episode 4
A developer's week on Tequila: one feature, from a checkout attached to the real estate to a reviewed deploy, and a rollback that is one line in the history.
Episode 5
Identity and access on Tequila without a vendor: the estate runs its own identity — a users pool and an invite-only admin pool, tokens verified locally with the estate's own keys, service clients, and OpenID Connect on your own domain.
Episode 6
What happens when the platform moves: a release fans out as a pull request that carries its render, the secrets doctor speaks before the merge, Flux applies, and the way back is one revert.
Episode 7
What tequila.yaml decides: who you are, where you run, what you run and what the estate provides — one file in the gitops repository, reviewed like code, and the gate nothing passes without.
Episode 8
Who does the work when there are three of you: a tenant workspace comes with a team of eight named roles that take a product from the idea to production on the platform's rules — and every decision stays the founder's.
Plays from youtube-nocookie.com once you press play. The channel on YouTube
Why Tequila
- You write only your domain.
- Identity, audit, files, media, notifications, chat, an admin area and package registries ship as platform services: built once, running in production, pinned by version. The services
- A running estate in an afternoon.
- One command turns a GitHub organisation into a tenant. One more puts the whole estate on a developer’s machine, with real TLS and nothing to fill in. From an empty org to production
- Audit-ready from the first commit.
- Every change is an event. The audit trail is hash-linked, re-verified in a service of its own and anchored outside the estate every day. The controls are mapped to SOC 2, ISO 27001, GDPR, HIPAA and Ukraine’s Law 2297-VI. Compliance from the box
- An AI team in every workspace.
- Eight Claude Code roles, from product analyst to operator, take a product from the idea to production on the platform’s own rules. The decisions stay yours. The AI team
- Yours, end to end.
- Your organisation, clusters, cloud account, users and keys. Renders are plain YAML in your repository, the cloud is OpenTofu in your account, and Tequila holds no access to your clusters: what you run, you pull from signed releases. How rendered GitOps works
From an empty organisation to production
Four steps. Tequila walks each of them itself, every day.
- 1
tq initYour org becomes a tenant
A gitops repository with one tequila.yaml, a workspace for the team, CI wired.
- 2
tq dev:bootstrapThe estate on your machine
Identity, data, messaging and your services on a reproducible VM.
- 3
php-service-templateA service from the template
Contracts, manifests and CI already wired, Tequila Core underneath.
- 4
git mergeEvery deploy a reviewed commit
Flux applies it. Platform releases arrive as pull requests; the estate reports back what runs.
What is in the box
Platform services, built once and pinned by every tenant. A new release reaches your estate as a pull request you review.
Releases as of 30 October 2026.
- IAMv0.52.6
Identity: user pools, hosted sign-in, invitations, social login, an OIDC provider, service credentials.
- Auditv0.13.9
The system of record: every service's trail copied and re-verified, anchored daily outside the estate, archived write-once, handed to auditors as evidence packs.
- UFSv0.12.13
Files: direct-to-bucket uploads, per-purpose policies, owner-scoped reads.
- Media conversionv0.11.13
Image and video derivatives, produced the moment a file lands.
- Notificationsv0.8.8
User-addressed email with templates per locale and delivery tracking. SMS and in-app are next.
- Chatv0.7.11
Direct and group conversations on the realtime plane: presence, read receipts, attachments.
- Broadcastv0.7.13
Announcements to audiences and guests: banners, a bell, read state.
- Jimadorv0.17.5
The admin area: one application per estate, a module per service, every action audited.
- Packagesv0.34.6
Private Composer, npm and container registries on your organisation's sign-in.
- Sitesv0.2.5
Static sites and landings served by the estate, published from CI.
- Paymentsv0.7.3
One charge split at the provider, never custody: payment intents, refunds, a store-first webhook inbox, a ledger. Card numbers never enter the estate.
Underneath
- Tequila CoreDDD, event sourcing, the outbox, typed buses
- MongoDB ODMPersistence built for event sourcing
- Klass8sKubernetes manifests as typed PHP classes
- OperationsThe estate as code, rendered per environment
- ContractsOpenAPI everywhere, PHP and TypeScript generated
- tqOne CLI for the whole lifecycle
- tq-operatorReports what each estate runs. Open source
An AI team that knows the platform
Every tenant workspace is a Claude Code root with the platform’s rules, decisions and docs loaded, and eight named roles. Their work lands as files and pull requests you read. Production stays behind your merge.
How the team works- Product analyst
- The job, the money, what not to build
- Architect
- Bounded contexts, services, pins
- Compliance officer
- Regimes, controls, evidence
- Payments specialist
- The money flow, the provider, a split without custody
- Builder
- One work order, one pull request
- Reviewer
- Defects against the order and the rules
- Operator
- Environments, releases, runbooks
- Consultant
- The platform’s answer, with the page
Built on itself.
One file declares an estate. Tequila’s own runs this site, the console and the identity plane on the same repository shape, the same commands and the same releases every tenant gets.
org: acme domain: acme.com environments: dev: { cloud: generic } # a VM per developer prod: { cloud: aws } # EKS + Atlas services: iam: { version: v0.52.6 } audit: { version: v0.13.9 } orders: {} # yours
Tequila opens by invitation.
We bring tenants on in small groups, so each one has our full attention from its first commit. Tell us what you are building: a person reads every request, and the invitation arrives at the address you leave.
Rather talk first? sales@tequila.dev