Platform
How we build, and what checks it
A large share of the first draft is written with AI assistance. None of it merges until a named engineer has read it.
Who does what
The AI drafts, a person signs
Every activity on a project has a named first author, a named reviewer and a named sign-off, and the named engineer is the person you meet at the increment demo.
Application code
- First draft
- AI-assisted
- Reviewed by
- Named engineer
- Signed off by
- You, at the increment demo
Tests
- First draft
- AI-assisted
- Reviewed by
- Named engineer
- Signed off by
- The pipeline, on every change
Infrastructure
- First draft
- Named engineer
- Reviewed by
- Second engineer
- Signed off by
- Your security contact
Data migration
- First draft
- Named engineer
- Reviewed by
- Second engineer
- Signed off by
- You, against a rehearsal
Release to production
- First draft
- Named engineer
- Reviewed by
- Second engineer
- Signed off by
- You, at the demo before it
Scope and price
- First draft
- Named engineer
- Reviewed by
- You
- Signed off by
- You, in writing
The review gate
Four checks before anything merges
In order, on every change, with the reviewer's name on the record.
01
Does what the increment said
The scoped plan lists what each increment ships; a change that does something else goes back.
02
Safe to run
Inputs validated, no secrets in source, and a test for anything that touches your data.
03
Readable by your team
Your team inherits the code, so a change only its author can read is rewritten.
04
Deploys from a clean checkout
The pipeline runs on every change; a change that needs a hand-run step is not finished.
Two ways to work
Hand it over, or we run it
The application code is yours from the first commit under both, and under both you ask for changes in the same portal, Project Matrix. What differs is who runs production.
We build it, you run it
| Artifact | In your hands from |
|---|---|
| Source repository | The first commit |
| Cloud account and infrastructure | Discovery, in your name |
| Deployment pipeline | The first increment |
| Runbook | Handover, walked through over 2 sessions |
| Our access | Revoked on the handover date |
| Our access, if Matrix keeps shipping changes | One scoped deploy role you grant, shown in the portal and yours to revoke |
Matrix ships to your cloud from a GitHub mirror of your repository. We say so before you sign.
We build it and run it
| Artifact | In your hands from |
|---|---|
| Source repository | The first commit |
| Repository transfer | On request, to an organization you name, without waiting to leave |
| Dashboards, exports and reports | The first increment |
| Your data and your request history | Any time, and again in the 30 days after you leave |
| Cloud console | Never. Ask for your own account and we build there instead |
| The environment | Never. It is torn down 30 days after you leave |
There is no handover date and no infrastructure transfer: your code and your data leave with you, the platform stays ours.
See a project in that shape
A price and a rough number of increments in 5 working days, before you pay for anything.