Open Cradle
Sign in
ENRU
One project · one team

Agents do the work. Cradle checks it.

Every Cradle project is a team: a captain who assigns, leads who deliver, and a checker who signs off before anything reaches you.

Get startedSee how a project runs
Triage · captain
Checker
DEV
CONTENT
DATA
How a project runsPlanned

You hand over a task. You get back a result that has been checked.

01 · Assign

The captain takes the task and hands each part to the right lead.

02 · Deliver

Leads work with their executors until the result is ready to show.

03 · Check

Each lead shows the result to the Checker, which tests it against your rules and data.

04 · Return

Only approved work goes back to the captain, and then to you.

Cradle Server

Install it on any server. Each team picks its cradle.

Cradle Server runs on a laptop, a server or a GPU rack. A cradle is the place where a team's models, knowledge and results live.

01 · Install

On your hardware

A GPU runs larger models. A plain CPU works too, with smaller models and less speed. The same server, either way.

02 · Connect

In the web console

Each project, which is a team, gets the address of its cradle. One cradle can serve several teams, or each team can have its own.

03 · Or skip the installPlanned

Use the Cradle cloud

Ready workers, a database and cloud models through Bedrock. Good for trying a team before you move it home.

Inside a cradle

Everything runs in containers on the same server, so data stays where you put it.

Models

Open-weight models on your GPU or CPU.

Knowledge base

The documents and rules the team works from.

Results database

Every result, with the check that approved it.

The team

Captain, leads, executors and Checker.

Example · a dev teamPlanned

A team that turns a ticket into a spec.

Triage takes the ticket, Team Lead writes the spec, developers implement it, DevOps deploys.

Spec

  • TLWrites the spec in the repo format
  • RSFinds the related code

Build

  • D1Implements and tests
  • D2Implements and tests

Deploy

  • DODockerfile, CI
  • DPDeploys and verifies

Today: the template creates the team; routing picks one agent per ticket. The hand-off chain is planned.

In your chatPlanned

Put an agent in your group chat.

Connect an agent to Telegram or WhatsApp. It reads the thread, picks up what was agreed, and files it as a task in the project.

Let's move the launch to Thursday and send the new price list to Anna.
Agreed. I'll update the landing text.
Added to project Launch: 2 tasks, owners and dates set.

Cradle

The team and the models behind it. One endpoint for any model, and a project for every team of agents.

Open Cradle →

Smart Notes

Say it out loud and it is written down. Voice and screenshots become a work journal you can search.

Open Smart Notes →
Where it runs

Pick a place. Switch any time.

Your machine

Start on a laptop with a small local model.

Your GPU server

Move to your own hardware. Your data stays on it.

HostedPlanned

A ready worker with cloud models, for trying it out.