Bring your own tools
A blank canvas for work
Every shell is yours. Install the tools you already use — the cloud already has what you need.
Skip the next hire
Your AI Cofounder, everywhere you work.
Meet it from the App. Connect it from Settings when you work in your own tools. One cofounder, every surface.
Checking healthService status: Checking health.
Opens the Armalo workspace — sign in first if you haven't already.
What you get
Files stay put
State survives between sessions
Your files and history stay across restarts. Come back later and pick up where you left off.
Per-second cost
Pay for what runs, not what it might run
The cloud is yours only while you're using it. Stop it from the App and the meter stops. Resume later and pick up exactly where you left off.
Your model keys
Your inference account, your terms
Connect the providers you already trust. Keys never touch a shared model pool — the cloud is yours because the keys are yours.
No extra layer
You decide what runs
There's no extra layer between you and the work. You decide what runs. The cloud does what you tell it to do.
What's underneath stays out of the way
You don't need to know the stack
You don't pick what runs underneath, and that's deliberate. You don't need to know what's underneath to use what runs on top.
After you open the App
The App is the path today. Settings → Developer is the honest connect path. The unpublished CLI stays secondary.
- 01
Open the App
Meet your AI Cofounder from the App. That is the live path today.
Open in the App → /start/go - 02
Connect from Settings
If you work from your own tools, connect once from Settings → Developer. MCP is the honest checkout path.
Settings → Developer → Connect once - 03
The CLI is unpublished
Do not install @armalo/cli from npm. If you have an App checkout, the unpublished CLI lives there and stays secondary until a human publish.
# App checkout only — not npm node packages/cli/bin/armalo.mjs login
Available on every tier
Cloud rides any paid Armalo subscription. Pick the tier that matches how much parallel work you run and how much priority support you want.
Solo$29 / mo
Personal cloud, 1 active shell, pooled disk, email support.
Growth$79 / mo
Up to 5 parallel personal shells, files that persist, priority support queue.
Scale$199 / mo
Higher shell ceilings + dedicated support + priority scheduling.
Enterprise & AgencyCustom
Dedicated cluster, BYO cloud, named solutions engineer, air-gapped Helm installer.
Existing customers with Starter workspaces can keep using workspaces; the shell is opt-in, never a forced migration.
Common questions
Is this the same Armalo workspace surface?+
No. Workspaces are the multiplayer canvas. The shell is a single-person machine for focused work. You get a place to work, not a shared room.
Can I install the CLI from npm?+
No. The App CLI is unpublished. Open the App, or connect from Settings → Developer. Do not install @armalo/cli from npm.
Do I need the CLI today?+
No. Open the App. If you work from your own tools, connect once from Settings. The CLI is unpublished and secondary until a human publish.
Can I bring my own model keys from day one?+
Yes. Every shell ships with no inference key of its own; you connect the keys you already have.
What about state, secrets, and disk persistence?+
Your files and installed tools persist across restarts. Secrets stay inside the shell. The visible contract is the connect endpoint, nothing else.
Ready to meet your Cofounder?
Open in the App. The CLI is unpublished — do not install it from npm.
Opens the Armalo workspace — sign in first if you haven't already.