Any model does the work.
Dagpilot proves it's done.
Hand off a task. Dagpilot draws up the contract, runs the work on your machine with your own AI subscription or key, verifies every check and merges with proof. Three AI models have already shipped work through this layer.
Google sign-in didn't finish — no problem. Continue with your email below instead.
Runs on your own servers. Every merge carries its proof — 731 subtasks verified as of July 2026.
Runs on the models you already use — auto-detected from your key
How the night shift works
One task in, one verified merge out. Four stages run without you.
Decompose
Dag turns your task into a dependency graph of small verifiable steps.
Execute
Each step runs on your own server with full project context.
Verify and heal
Every step is checked against a compiled contract. Failures are repaired and retried.
Merge with proof
The branch merges only when the checks are green. The report shows the whole night.
Wake up to the Night Shift Report.
Every run ends with a report you can read in ten seconds and share with one click. What was done, how long it took, what was verified and what it cost. Numbers, not adjectives.
Night shift complete
Add rate limiting to the public API
Shipped autonomously by Dagpilot and verified per contract.
The night shift isn't only for code.
Dag ships any deliverable with a checkable definition of done — research, analysis, audits, strategy. Decomposed, executed, verified per contract, delivered as a report.
Research shift
Competitive landscape of 14 rivals
Every claim traced to a source. Verified per contract.
Finance shift
Trading post-mortem for the quarter
Numbers recomputed from raw data. Verified per contract.
Marketing shift
SEO audit and a 90-day content plan
Plan tied to audit findings. Verified per contract.
Any market the task brief can name — and it names them all:
- Finance · Trading
- E-commerce
- SaaS
- Social
- Gaming
- Health
- Education
- DevTools
- Web3 · Blockchain
- AI · ML
Target user, platform, domain, scale, budget — the Product Brief shapes every shift. If the deliverable has a checkable definition of done, Dag runs the night.
You stay in control.
Autonomous doesn't mean unsupervised. Every shift runs inside limits you set — and nothing red ever merges.
A hard budget per task
You set the ceiling before the shift starts. Dag tracks its own spend and stops before crossing it.
Rollback anytime
Automatic snapshots before every step and repair. One click restores the exact previous state.
Red never lands
A branch merges only when its compiled contract passes. Failures stay on the branch with a full trace.
Self-hosted, always
Your servers, your keys, secrets encrypted at rest. Pause or cancel any shift at any moment.
Dagpilot ships Dagpilot. Its own nightly shifts run on this very product — 233 contract checks green, every day.
Where this is going
On the roadmap — designed, not built yet. The trust layer we are building toward, in the open. None of this ships today:
Execution Passport
Every piece of work will carry a living record of what was proven about it — and by which model.
Evidence Ledger
An append-only journal of every verdict, so proof will survive any model swap.
Re-verification on model change
Accepted work will be re-checked when the model that verified it is replaced.
A measured reliability graph
Models will be ranked by verified work on real tasks — not by benchmarks.
Plans for every night shift.
Bring your own models and machines — Dagpilot runs the shift. Every plan keeps the full contract. Free while in beta.
Free
$0
Try the night shift on one project.
- 3 night shifts per month
- 10 asks per day
- 1 connected machine
- Full verify, heal and gated merge
Pro
$20 / month
For a developer shipping every week.
- 15 night shifts per month
- Unlimited asks
- 3 machines, 2 shifts in parallel
- Every pipeline: research, spec, full
Max
$200 / month
For teams of projects, not teams of people.
- 100 night shifts per month (fair use)
- 25 machines, 5 shifts in parallel
- Priority support, early access
- Hosted compute — coming soon
Enterprise
Let's talk
Custom limits, dedicated support, your terms.
- Custom shift and machine limits
- Invoiced billing
- Dedicated deployment — on request
- Dedicated support and onboarding
Your tokens bill to your provider — Dagpilot never marks them up. Details and FAQ on the pricing page.
Frequently asked questions
Short answers first. Ask the rest on X.
What is Dagpilot and how does it work?
Dagpilot is an autonomous engineering system. It takes a task in plain language, decomposes it into a graph of small steps, executes them on your servers, verifies each one against a compiled contract and merges the result. You review a finished, tested pull request instead of babysitting an assistant.
What happens while I sleep?
Dag works through the graph step by step. When a check fails he repairs the step and retries. In the morning you get the Night Shift Report with the timeline, the verification results and the merged branch.
How is this different from a coding assistant?
An assistant waits for your next message. Dagpilot takes the whole task. It plans the graph, writes each step, verifies the result against a contract and merges only when the checks are green. You read one report in the morning instead of a hundred replies at night.
What do I need to run it?
A server you control and a model API key. Dagpilot connects to your machines over SSH, keeps the code there and opens a pull request when the work passes its checks.
Is Dagpilot only for code?
No. Research, analysis, audits, documentation and strategy are first-class shifts. Dag detects the domain of the task and verification adapts — contracts check the delivered documents instead of runtime tests. The morning ends the same way: a Night Shift Report with proof.
What does a night shift cost?
You decide. Every task starts with a hard cost cap; the shift tracks its own spend and stops before crossing your limit. The report shows the exact cost of the night, so the worst case is always the number you chose.
Is my code safe?
Dagpilot is self-hosted: your repository lives and runs on your own machines — we never clone or copy it. What we keep is what it takes to show you the work: your task text, the results and logs, and what it cost — results can quote the code your worker wrote. Secrets are encrypted at rest, merges are gated by verification, and nothing is published unless you explicitly share a report.
Hand off your first task tonight.
Connect a machine, describe the task and go to bed. The report will be waiting in the morning.
Try Dagpilot