Skip to content

Setup flow

OneCamp Cloud

This guide is for OneCamp Cloud subscribers. You do not install anything and
you do not need a server: one is provisioned for you, and it is yours alone.

If you bought a one-time licence instead, you want Installation.

What you get

A whole server, running only your workspace. Not a row in a shared database,
not a schema alongside other customers — your own machine, your own Postgres,
your own file storage, your own encryption keys.

That is more expensive for us and it is the point: there is no query anywhere
that has to remember to filter by your account, because there is nothing else on
the machine to filter out. It also means we cannot read your data, and cannot
restore it for you from some central backup, because there isn't one.

1. Name your workspace

After you subscribe, open your account page and
choose a name. Your workspace becomes:

yourname.onemana.dev

Pick carefully — it is the address everybody types. You can move to your own
domain later, but the name is how your team finds you in the meantime.

2. Wait for it to be built

Setting up a machine takes tens of minutes: ordering it, preparing it,
installing, issuing certificates. Your account page shows where it has got to,
and we email you when it is ready.

If it is taking unusually long, that is visible to us too and somebody is
already looking at it. You do not need to report it.

3. Sign in

The "your workspace is ready" email carries the address, your username, and a
generated password. Change that password after your first sign-in. We keep no
copy of it — that email is the only place it has ever existed.

4. Switch on email — do this first

Your workspace ships unable to send email. That is deliberate: we will not
send from your domain until you choose to, so we leave the key blank rather than
picking one for you.

Until you add one, it fails silently. An invitation is created and never
arrives. "Forgot password" says "check your email" and nothing comes, because
that page gives the same answer either way by design.

Add a sending key in your workspace under Admin → Settings → Email. It takes
a minute, and it is what lets everyone on your team recover their own account
without contacting anybody.

5. Everything else, in your admin panel

None of it needs a config file or a server login.

  • Google / GitHub sign-in — your own OAuth client id and secret.
  • AI — choose a provider and paste your key, or run models locally. We do not
    ship a model and we do not resell inference; the key is yours and so is the
    bill.
  • Upload limits, allow-lists, two-factor — all in the same panel.

Using your own domain

You can move your workspace to a domain you control. On your account page, enter
the domain and we show you the DNS record to create. Add it, then press check.

We verify the record actually resolves before switching anything over, so a
mistyped record leaves your workspace exactly where it is rather than taking it
offline.

If you are locked out

Your admin password is set once and never stored, so it cannot be looked up or
resent — a new one is the only way in. Tell us and we will issue a one-time reset
link to the address on your account. You choose the new password; we never see it.

Two things make this quicker if they are true before you need it: switch email
on
(step 4), so your team can reset their own passwords without us, and keep
your recovery codes
if you turn on two-factor. If both the authenticator and
the codes are gone, we can clear the second factor for you, but we will want to
be sure who we are talking to first.

Your licence key

A subscription includes the self-hosted licence too, and it is on your
account page with the command to install it.

One key covers both editions — v1 without AI and v2 with it — and the
installer asks which you want. If you ever lose it, sign in and copy it again; it
is always there.

It stays yours. Cancelling the subscription ends the hosting we run for you, not
the licence.

Updates

We update the workspace for you. You do not download anything and there is
nothing to run.

Being straight about where this stands today: updates are applied by us rather
than on a schedule you can see, and there is no page showing which version you
are on. If you want a specific fix, ask and we will tell you whether it has
reached your workspace.

Cancelling

You cancel from your account page, and nothing dramatic happens immediately.

  1. Your workspace keeps running to the end of the period you have paid for.
    There are no refunds and no partial months; you simply keep what you bought.
  2. Then it becomes readable but not writable for 14 days, so you can export
    anything you want to keep.
  3. Then the machine is wiped — a real disk erase before it is released — and
    the data is gone. Not archived, not held for a while. Gone.

We email you before each of those steps. If you resubscribe during the export
window your workspace comes straight back; after the wipe it cannot.

What this does not include

Being honest about the edges:

  • No central backup. One machine per customer means there is no fleet-wide
    restore. Export what matters to you.
  • Calls need a LiveKit server, which the standard build does not run.
  • Mobile push needs Firebase credentials, which most workspaces will not have.

Anything here that you would rather run yourself, you can: every Cloud
subscription includes the self-hosted licence, and the product is the same
product. You would just be bringing the machine.