Architecture-first backend generator
Design the backend system before you write it.
Describe your product. Delta AI designs a scalable, secure backend architecture, writes the specification for every service, and opens the pull requests in your GitHub organisation. Your code, your cloud, no lock-in.
Your repos
One repository and one container per service, in your GitHub organisation.
- delta-chat / messagingGo
- delta-chat / mediaRust
- delta-chat / notificationsTypeScript
A spec per service
Written before any code, in parallel.
You review
Plan approval before each step. Nothing merges without you.
Free first run
The first architecture and one full service. No card.
Six steps, one conversation
Describe
plain language
Architect
services, edges, stores
Approve
optional, per step
Specify
one spec per service
Implement
code against the spec
Review, deploy
PRs in your org, your cloud
Months later, a feature is a new message. A fix is a Refactor that stays inside the design.
What lands in your organisation
delta-chat / messaging #1
feat(messaging): persist channel history and fan out message.created
- Branch
- delta/cs-7b5b58fe/messaging-service
- Checks
- 66 passing tests
- Diff
- 18 files changed
docs / architecture.md
Key architectural decisions
- Single writer per channel, ordered by a monotonic sequence.
- message.created published after the write commits, never before.
- Retention is a table policy, not application code.
- Fan-out is asynchronous so a slow consumer cannot block a send.
What you get
- Repositories per service
- Each service gets its own repository in your organisation, with its own history and specifications.
- Pull requests in your org
- Changes arrive as pull requests you can read, comment on and approve. Delta never pushes to your default branch.
- A Dockerfile per repository
- Every service builds to one container image. The build is standard, so your existing pipeline can take it.
- Standard components
- PostgreSQL, Kafka, S3 compatible storage and Docker. No proprietary runtime and no framework lock-in.
- Plan approval
- Turn on plan mode for architecture, specification or implementation. Each enabled step waits for you.
- Change sets
- Pull requests that belong to one feature are grouped. Delta merges the group once every PR is approved.
The method
Built by a method you can read
Every design decision is written down, in the same vocabulary, in every project.
- Services around domains
- Each owns one job and its data.
- Communication with intent
- Sync for answers, events for everything else.
- Contracts first
- Inputs, outputs and errors before code.
- The right runtime per service
- Python, TypeScript, Rust or Go. Delta picks, or you fix one.
- Observability from day one
- Traces, logs and business metrics in every service.
Worked example
The four messages behind the diagram
A real-time platform like Discord: communities, chat, voice and video, friends, moderation.
Not yet
Hosting
You deploy the containers. Managed environments are coming.
Deploy
Delta stops at merged code. Your pipeline takes it from there.
Front-end
Backend only. Delta does not generate a UI.
Existing repos
Delta creates its own repositories. It does not import yours.
Free
First architecture and one service, free.
100 chat messages, with the system design and service diagrams. No card.
Design your first backend, free- Free
- Free forever
- Discovery
- $25 a month, 25 monthly credits
- Pro
- $50 a month, 50 monthly credits
- Business
- $200 a month, 200 monthly credits
- Credits
- $10 minimum, never expire, plans cost less per credit
Delta designs and writes your backend system. You deploy the containers wherever you want. Managed environments are coming; they are not included yet.
What is different
Designs the system first
- Coding assistant
- If you ask
- Backend platform
- No
- Delta AI
- Always
Design and code stay in step
- Coding assistant
- No
- Backend platform
- No
- Delta AI
- Across every repo
You own
- Coding assistant
- Your code
- Backend platform
- Their platform
- Delta AI
- Your code, standard parts
Hosting
- Coding assistant
- Yours
- Backend platform
- Theirs
- Delta AI
- Yours, for now
Questions engineers ask
Is it secure?
Contracts before code, one data store per service, secrets never in code, and nothing merges without your review. Nobody honest says "100 percent".
Will I be locked in?
No. Your GitHub organisation with services built on PostgreSQL, Kafka, S3 compatible storage and Docker. Leave with everything.
Which languages?
Python, TypeScript, Rust and Go. You can let Delta choose per service, or fix one runtime for the project. Changing a service to another language can be part of a feature when it requires it.
Do I need a subscription?
No. The free tier covers the first architecture and one full service. After that you can buy credits from $10, or choose a monthly plan with matching credits.
What about hosting?
Delta designs and writes your backend system. You deploy the containers wherever you want. Managed environments are coming; they are not included yet.
How do I review the code?
Every change arrives as a pull request in your GitHub organisation. Read the diff, request changes, approve. For grouped change sets, approve rather than merge: Delta coordinates the merge once every PR is approved.