Ninja
Open the console

Run 0417 · started 05 Sep 2026, 06:00 UTC · still open

Close the lid. It keeps working.

Most AI stops when the conversation stops. Ninja is built the other way round: you hand over a piece of work, it holds the thread for hours or for weeks, on its own machine, and it is still going when you come back.

Open the console Book a walkthrough

Runs unattended

Nothing on this page needs a person watching it. The work is checkpointed, the state survives a failed step, and a run picks itself back up where it stopped.

Horizon
Minutes to weeks
Tools reachable
3,000+
Models
Frontier or open weight
Runs in
Your cloud
People using it
500,000+
T+00:00What a horizon looks like

The length
of the job
is the whole point.

A chat assistant is measured in seconds and a copilot in keystrokes. The work that actually costs a company money is measured in days: a migration, a close, a queue that has to stay held, a review that nobody finished. Those are the runs Ninja is built around.

The scale below is logarithmic, from one minute to one month. It is drawn to show the shape of the problem, not a benchmark.

Answer a questionOne turn
40 s
Draft a document and check itOne sitting
6 min
Reconcile a month of invoicesUnattended
4 h
Move a service to a new APIUnattended, checkpointed
3 d
Sweep a literature base to a decisionUnattended, resumable
11 d
Hold a support queueStanding
Open
  1. 1 min
  2. 1 hour
  3. 1 day
  4. 1 week
  5. 30 days
T+04:12Duty cycle

Your week
has holes
in it.

Friday evening to Monday morning is sixty-four hours in which nothing moves. Ninja does not observe them.

Ninja Your team MonTueWed ThuFriSatSun
Trace 01 · one week · illustrative
T+19:40What makes a long run possible

Four things
a chat window
cannot do.

None of this is a bigger model. It is the machinery around one: somewhere to keep state, somewhere to run, a way to come back from a failure, and a place where a human still has to say yes.

01

Memory that outlives the window

Context does not reset between steps or between days. On the paid tiers the working memory is intentionally not the thing you have to manage.

02

Its own computer

A run gets a machine, a filesystem and a browser of its own, so it can install, fetch, edit and re-run without borrowing your laptop.

03

Recovery without you

State is persisted as the work advances. A step that fails is retried from the last good point instead of taking the whole run down with it.

04

A stop before the risky move

Actions that touch money, customers or production wait for a person. Everything else keeps going while they wait.

Read how a run holds

T+02:11:56Where the work happens

In your cloud,
on your models,
on your metal.

Ninja deploys as software you run, not only as a service you send data to. It can sit inside your own virtual private cloud on AWS, Azure or Google Cloud, or on machines that never touch the public internet. The model underneath is your choice, frontier or open weight, and it can change without the work changing.

Deployment options

BoundaryAvailable
Managed serviceYes
Your VPC, AWSYes
Your VPC, AzureYes
Your VPC, Google CloudYes
On premisesYes
Air gappedYes

Hand it
something long.

The free tier runs real work, not a demo. Give it the job you have been putting off since March and come back tomorrow.

Create an account

Talk to a human first

Both links open the real product.