Your competitors sleep at night. Your processes don't.At night, our AI agents move your work forward. In the morning, your team decides.

Your technical team has more tasks than hours. Some are precise, verifiable, and have been waiting for weeks: a test to write, a migration to finish, some debt to pay down. The night team takes them while you sleep. Each task is handled by an agent on its own branch, checked by a second agent, and waits for you in the morning with a readable handoff. You accept, reject, or send it back with a note. Nothing reaches production without you.

Start a pilot

Your situations

Who it is for

A technical team of two to fifteen people, with a git repository and an overflowing backlog.

Clear tasks that never make it ahead of the day's emergencies.

A technical lead who wants to test agents on real code without handing over the keys.

A team that has tried a coding assistant and wants to move from copilot to delegation, with guardrails.

What we deliver

What the night does

One session per task

Each backlog task is handled by a dedicated agent session, on its own branch, within the paths the task allows. One task, one branch, one proposal.

A check by another agent

Before you read anything, a second agent replays the task's completion criterion and signs its report. The night declares, the checker checks, you decide.

A readable handoff in the morning

For each task: what changed in three lines, whether the criterion was met, the deviations reported, what to look at first. A draft merge request carries the code.

A review after four weeks

How many proposals, how many accepted, how long it took to decide, what it cost. You decide to continue or stop on figures measured on your own code.

How it works

How the pilot runs

Written agreement and access
One repository, the allowed paths, what the agents may read, who decides. Write access to dedicated branches, never to the main branch.
Starting backlog
We write the first tasks with you, to the template: what it changes, a machine-verifiable completion criterion, what must not be touched.
Four weeks of nights
The agents work at night, the checker signs, your team decides in the morning from the merge request or the decision queue.
Review and decision
Acceptance rate, time to decide, cost per accepted proposal. You continue on a subscription, with the €1,500 of the pilot deducted from the first month, or you stop.

What the night does not do

It never merges. It never deploys. It never writes to your main branch. It stays within the paths the task allows, and it never writes a secret into the code.

When a task has no verifiable completion criterion, it fixes nothing: it prepares. It reproduces the problem, writes the failing test, prices two approaches, and lets you choose.

Three signatures on every proposal

The executor declares what it did. The checker, another agent, replays the completion criterion and signs. The decider, a human on your team, accepts, rejects, or sends it back with a note. A proposal without its three signatures does not enter your code.

Where it comes from

We have been running this night team on our own projects since 24 September 2026: our website and our agent platform. Every night proposal there is traced in our GitLab issues, with its handoff, the checker's report and the decision. The pilot gives you the same thing, on your repository.

What you need to plan for

One person on your team who reads the proposals in the morning; a quarter of an hour is often enough. Access to your git forge. And precise tasks: the clearer the completion criterion, the more useful the night.

References

What already runs

Since 24 September 2026, our agents have been working at night on our own projects; every proposal goes through a checker before a human reads it in the morning.
Every handoff, every check report and every decision is written in our GitLab issues, timestamped and open to review.

Frequently asked questions

Who writes the tasks?

At the start, we write them with you, to the template: goal, completion criterion, allowed paths. After that, your team adds more whenever it wants, and we can suggest tasks from your backlog.

What happens if a proposal is bad?

You reject it, or send it back with a note: the next night picks up from your note. A rejected proposal leaves only a branch you can delete.

Does my code leave my company?

The agents read the code in the allowed paths to work on it, and the language model receives it to process it. The written agreement sets what may be read, and what must never be.

How much does it cost afterwards?

The pilot costs €1,500 excl. VAT for four weeks. The subscription price is set at the review, based on task volume; the €1,500 of the pilot is deducted from the first month.

Does it replace a developer?

No. The night takes the precise tasks your team has no time for. Judgement, architecture and the decision stay with you, every morning.

Four weeks to measure it, on your code

One repository, one written agreement, €1,500 excl. VAT deducted from the first month of subscription.