Quickstart
From sign-up to first paying customer in ten minutes.
Five steps. Same shape whether you are founder, agency operator, or enterprise lead. The first step takes thirty seconds; the rest is the agent working.
- 01
Sign in with Google at app.armalo.ai/start/go
Open https://app.armalo.ai/start/go in any desktop browser, pick the Google account you want to run the workspace under, and confirm. The workspace is yours in about thirty seconds — the agent is already in the room, the canvas is on the right, presence is live.
Open app.armalo.ai/start/goStep 01 — preview frame placeholderhuman turn → authenticated gateway → server-ordered room event log → turn arbiter → AgentEngine (Hermes by default) → sandbox (E2B microVM) → streamed events, artifacts, missions, audit receipts - 02
Fork a catalogue template
The catalogue ships two live templates (SaaS Landing + Stripe Checkout, Agency Client Portal) and four more in development. Pick one; forking into the workspace carries the seed data, the design tokens, and the integration configuration. If you would rather start from a blank canvas, just describe the outcome in the thread.
Browse the catalogueStep 02 — preview frame placeholderhuman turn → authenticated gateway → server-ordered room event log → turn arbiter → AgentEngine (Hermes by default) → sandbox (E2B microVM) → streamed events, artifacts, missions, audit receipts - 03
Customize the seed data
Tell the agent what to replace — the headline, the product names, the pricing, the colour. The thread is the spec; every edit produces a real diff on the canvas. Promotion gates (spec → review → test → deploy) run on every change, and you can approve, reject, or steer each gate from the chat rail.
Step 03 — preview frame placeholderhuman turn → authenticated gateway → server-ordered room event log → turn arbiter → AgentEngine (Hermes by default) → sandbox (E2B microVM) → streamed events, artifacts, missions, audit receipts - 04
Connect integrations
Stripe, Meta ads, WhatsApp, and email are managed integration packs with sandbox + live setups. Each pack has a pre-flight checklist (env vars, sandbox setup) and a verify-it-works path that ships an actual event to your sandbox account, then waits for the matching webhook before moving on. See the integrations page for the exact steps per pack.
Integration guidesStep 04 — preview frame placeholderhuman turn → authenticated gateway → server-ordered room event log → turn arbiter → AgentEngine (Hermes by default) → sandbox (E2B microVM) → streamed events, artifacts, missions, audit receipts - 05
Deploy to preview.<id>.armalo.app + a custom domain
First deploys go to a free preview.<id>.armalo.app URL — yours for ninety days, scoped short-lived credentials included. The Team tier adds custom domains, custom certificate provisioning via the Hetzner DNS layer, and the production hosting runtime. Every deploy is a checkpoint, not a project.
Step 05 — preview frame placeholderhuman turn → authenticated gateway → server-ordered room event log → turn arbiter → AgentEngine (Hermes by default) → sandbox (E2B microVM) → streamed events, artifacts, missions, audit receipts
One checklist before you go live
- Confirm the Stripe webhook URL is set to the production endpoint the platform minted.
- Move the custom domain DNS to Cloudflare and attach it to the preview workspace.
- Invite a teammate into the workspace — they share the same thread, the same canvas, the same turn arbiter.
curl -fsS https://app.armalo.ai/start/go
# or, if you're running the platform locally:
corepack pnpm install --frozen-lockfile
corepack pnpm dev