1
Create an account
Sign up at scaling.cloud/sign-up and verify
your email.TODO: replace before launch — say which sign-in methods are enabled.
2
Land in an organisation
Every account belongs to at least one organisation, and all product data is
scoped to it. A caller without an active organisation cannot read anything.On first sign-in you either create an organisation or accept an invitation.Leaving happens the same way, in reverse. When an owner removes you from an
organisation, that membership ends by itself — there is nothing to cancel
here, and nobody has to run anything on our side for it to take effect.
Calls you make against that organisation stop answering within seconds, and
the membership is gone rather than hidden: nothing that counts members or
organisations counts it afterwards.Being removed from one organisation leaves your other memberships alone, and
it leaves your account alone. If you are invited back you start again as a
member of it, with no trace of the gap.
Right after sign-up the first request can return
not_found with
“Your membership is still being set up.” Your account is still propagating.
Retry; it resolves in seconds.3
Confirm the API is reachable
The API is its own host,
api.scaling.cloud, and deploys independently of
the application. /health is public and needs no credential, so it answers
“is the service up” before authentication is in the picture at all.Response
4
Make one authenticated call
/me is the smallest call that exercises the whole chain: a verified
credential, a bound organisation scope, and a scoped read. If it works,
authentication and tenancy work.Authenticating means signing in with OAuth.TODO: replace before launch — the OAuth flow is not settled, so this step
cannot yet be walked end to end.Walked through in full in Your first API call.5
Do the thing this product is for
TODO: replace before launch. This is the step that matters and the only one
the template cannot write for you. Everything above is plumbing; the reader
came for this.