Private beta · onboarding the first 20 teams
Real phones.
Real apps.
One control plane.
Cradle turns a room full of phones into a fleet you can actually run. See every device, assign the accounts you own, schedule posts, and watch each one publish on a real device — step by step, with a record you can trust.
Free during the beta. No hardware needed to try — or ask us to set it up for you.
- TIPixel 8@northwind.studio · TikTokPublishing
- INGalaxy S23@northwind.official · InstagramIdle
- XiPhone 13@northwind · XNeeds sign-in
- Prepare device
- Fetch media
- Open TikTok
- Attach video
- Enter captionnow
- Publish
- Verify
Two ways to start
Have us set it up, or see it working in the next two minutes.
We are onboarding twenty teams by hand during the beta. Either door leads to the same product.
We set it up with you
Tell us what you run and what you want out of it. We reply personally, set up your workspace, connect your phones — or lend you some — and stay close for the first weeks.
See it working now
No call, no phones, no install. A simulated fleet runs in your browser and takes a post from draft to published while you watch.
- 1Create a workspaceEmail or Google. Free during the beta.
- 2Run the simulated fleetOne button. Three phones appear, labelled Simulated.
- 3Publish a postWatch every step — sign-in, media, caption, publish, verify.
Why real phones
Running accounts at scale is a hardware problem wearing a software costume.
Emulators and APIs get you flagged.
The platforms reward what a real person does on a real device. Cradle does not imitate that — it uses it. The post goes out of the actual app, on actual hardware.
Phone rooms run on spreadsheets.
Which phone holds which account? Who has the password? What is it doing right now? Cradle makes that one screen with one source of truth.
You find out it failed tomorrow.
Every job reports every step as it happens. When something needs a person, it stops, says why, and says what to do — instead of failing quietly overnight.
How it works
Four steps from an empty workspace to a published post
Each step has a state you can see, and a next action when something goes wrong.
- 01
Connect a Farm Agent
A small program beside your phones. It calls out over HTTPS — no inbound ports, no firewall changes, nothing exposed.
- 02
Your phones appear
Every device it can see, with model, OS and connection state. Rented devices arrive the same way and sit in the same list.
- 03
Assign and sign in
Put an account on a phone and run sign-in. The agent types the credentials into the real app; Cradle never shows them again.
- 04
Schedule and watch
Compose, choose the format the app offers, pick a time. A device picks it up and you watch each step complete.
- 1
Post
Caption + media references
- 2
Scheduler
Due time reached
- 3
Device job
Queued for one device
- 4
Farm Agent
Leases and executes
- 5
Real app
Published on the phone
Media never travels inside a job. The agent asks for it separately and receives a short-lived, authorised download link.
The product
Six screens. Everything an operator needs, nothing they have to work around.
- FleetEvery phone, its health, what it holds and what it is doing. Owned and rented side by side.
- AccountsOne account, one phone, one session. Credentials go into a vault and never come back out.
- ComposerTikTok video or photo, Instagram post or reel, X, LinkedIn — with the settings each app actually asks for.
- ExecutionsEvery job, every step, timed. Retries happen on their own; things that need a person say so.
- RolesCreators make content. Admins run the fleet. Owners hold the keys. Enforced on the server, every request.
- Rent devicesNo hardware? Use ours. Rented phones are ordinary phones in your fleet — same screens, same schedule.
Composer
It knows what the app will ask for.
A TikTok photo post is not a video with the video missing. Cradle composes in the shape each app publishes — the right media rules, the right caption limit, the settings the app itself shows — and applies them on the device. Order your media, mark the cover, then publish now, schedule, or keep it as a draft.
TikTok
VideoPhotoTextOne video, up to 35 photos, or a text card. 4,000-character captions. Privacy, comments, Duet, Stitch.
Instagram
PostReelA carousel of up to twenty, or one vertical video. Share to feed, comments.
X
PostArticle280 characters, or a long post on Premium. Articles with a title. Who can reply.
LinkedIn
PostArticleUp to twenty images or a video, or a long-form article. Who can see it.
Built to be trusted
The boring security decisions, made properly.
You are handing this system the keys to accounts you have spent years building. It should be obvious how they are kept.
- Passwords are write-only.
- Stored in a vault, released only to a device that is signing that account in, and every release is logged.
- Media stays private.
- Uploads go from your browser straight to private storage. Devices get a link that expires in fifteen minutes.
- Agents are machines.
- A one-time token, a revocable credential, and outbound-only traffic. No user account, no inbound port.
- Roles are enforced, not hidden.
- Every request proves membership and permission on the server. Hiding a button is a courtesy.
What Cradle will not do
It never pretends to be a human.
- No CAPTCHA solving or security-challenge bypass.
- No anti-detection, fingerprint spoofing or platform evasion.
- No way into an account you were not given the password to.
When an app raises a challenge, the job stops and asks for a person. That is the design, not a limitation — Cradle is for operating accounts you are authorised to operate, on phones you are authorised to run.
Read the security summaryThe first twenty
Founding teams get the product shaped around them.
Twenty is the number we can genuinely look after by hand. When they are in, the door closes until the product has earned the next twenty.
What you get
- Your workspace set up with us, phones connected — or rented from us.
- A direct line to the people building it. Not a ticket queue.
- A roadmap that follows your fleet, not a generic one.
- Free for the whole beta.
What we ask
- Tell us what breaks, and what you wished it did.
- Thirty minutes every other week, while it is early.
- Run only accounts and phones you are authorised to run.
Who it is for
- Agencies running client accounts on real devices.
- Brands with regional or multi-market accounts.
- Creator networks and studios publishing daily.
- Commerce teams posting product content at volume.
Try it without hardware
A whole fleet, in a browser tab, in one click.
The simulator is a real Farm Agent running in your browser. It registers, reports simulated phones, takes jobs and publishes — over the exact contract production uses. Cradle cannot tell the difference, because there is none. The only thing it fakes is the phone.
- 1Press ConnectSigned in, Cradle creates the agent for you. Nothing to install or copy.
- 2Phones appearUp to four, labelled Simulated everywhere so they are never mistaken for real.
- 3Break things on purposeTurn on failures, sign-outs and security challenges, and watch the recovery.
FAQ
Questions people actually ask
Do I need phones to try Cradle?
No. The simulator is a real Farm Agent that runs in your browser and speaks the exact contract a production agent uses. Register it, watch simulated phones appear, sign an account in, schedule a post and see it publish — end to end.
How does a post actually get published?
Through the real app on a real phone. Cradle decides what, when, for which account and on which device. The Farm Agent beside the phone decides how — opening the app, attaching the media, typing the caption, tapping publish — and reports each step back.
Where are my videos kept?
In private storage. Your browser uploads directly to it with a short-lived authorised link, and a device can only download a file while it holds a live lease on a job that needs it.
How are account passwords protected?
They go into a dedicated vault and are never stored in ordinary records, logs or job payloads. They are released only to an agent actively running a sign-in job for that account, and every release appears in your activity log.
What happens when a phone drops or an app signs the account out?
A dropped phone is retried automatically. A signed-out account or a security challenge stops the job, marks what needs a person, and says what to do. Nothing fails silently and nothing is left stuck.
Can I mix my own phones with rented ones?
Yes. Owned and rented devices are the same kind of thing in Cradle — same list, same states, same scheduling — so moving an account between them changes nothing else.
Your first post goes out in ten minutes.
Create a workspace, connect a simulated fleet, and take a post from draft to published — before a single phone is plugged in.