Skip to content
nacre.sh
— Getting started

Quickstart

From signup to a bot replying to messages in about 2 minutes. This is the happy path — nothing fancy, no DevOps.

Before you start

You'll need two things:

  • A valid payment method (credit card via Stripe).
  • An API key from at least one LLM provider — OpenAI, Anthropic, Google, OpenRouter, or any of the 290+ providers OpenClaw supports. See the LLM providers guide.

You do not need to install anything, bring a domain, or configure TLS. Nacre handles all of that.

Step by step

  1. Create an account

    Head to /signup. Email + password or Google. Verification is instant.

  2. Pick a plan

    On the pricing page, choose Solo, Team, Agency, or Scale. Annual billing gives you 2 months free. Plan changes require a delete-and-recreate cycle (see billing docs).

  3. Pick a region

    Singapore (SG), Ashburn US (US), or Falkenstein EU (EU). This is where your agent environment and its nightly backups live. You can't change regions after provisioning without a migration (contact support).

  4. Complete checkout

    Stripe handles payment. The webhook fires the moment your card clears.

  5. Watch the provisioner work

    You'll land on /app/deploying. Behind the scenes we provision your dedicated agent environment, set up a subdomain at user-<id>.nacre.sh, run cloud-init (Docker + Caddy + OpenClaw + agent), and wait for the first heartbeat. This typically takes about 2 minutes.

  6. Drop in an LLM key

    Once the dashboard opens, head to the LLM settings and paste your provider key. That's the only thing standing between you and your first bot reply.

  7. Connect a channel

    Add Telegram, Discord, Slack, or WhatsApp credentials under the Channels page. Your bot goes live on that channel within seconds.

What you get by default

Dedicated agent environment
Isolated instance — never shared with other users
HTTPS subdomain
user-<id>.nacre.sh with Let's Encrypt auto-renewal
Web terminal
JWT-gated bash shell at /app/terminal
Nightly backups
Encrypted tarball of /data to Cloudflare R2 at 03:00 UTC
Agent heartbeat
Uptime and health reported every 30 seconds
Stuck on the deploying screen?
The deploying page polls every two seconds and usually redirects on its own. If you're still there after two minutes, refresh. If the page shows an error state, email support@nacre.sh — we'll check the event log and either retry or refund you.

Next up