Infrastructure you can reason about
One way
to call everything.
Products, services and API credentials you make yourself. Every product is reached the same way — a signed HTTP request with a credential you created — so learning one is most of learning all of them.
- No card
- No sales call
- Free test credentials
- Off means off
One request shape
Learn one.
You've learned all of them.
Same request shape, same signature, same credential, whichever product is on the other end. The path changes. Nothing else does.
- Every request carries an HMAC over its method, path, query, timestamp and body.
- Nothing can be changed in transit, and nothing captured can be replayed.
- The client you wrote for the first product is the client for the tenth.
- The reference client is small enough to read in one sitting. Not a library to trust — a document to check.
Swap the path. Keep everything else.
The products
Each one small enough to understand in an afternoon.
Deliberately, because an afternoon is what you have. Switch on what a project needs and leave the rest off.
Sign-in
Login with Roola
OAuth2 sign-in for your own site. Roola never shares a password; you never store one.
Storage
Object Storage
Upload over the signed API, serve straight to browsers, and set a lifecycle so old objects age out.
Background
Queues
Hand work to a background worker and get on with the request.
Push
Realtime
Push events to a browser over a websocket.
Counting
Metrics
Count things and chart them over time.
Video
The Helix API
Channels, videos and search, from Helix — called the same way as everything else here.
Parliament
The Politicise API
Politicise, behind the same signature and the same credential as everything else.
The console
Console API
The console's own API, on the same signature. Documentation and a reference client for calling it come with it.
Announced · on the way
Secrets
Announced and being built. We'll say a date when we can keep it.
Announced · on the way
Edge Cache
Announced and being built. It will be counted the same way as the rest when it arrives.
Hold it in your head
The bill you can't predict. The console you can't understand. Not here.
Fear of your own infrastructure is a tax you pay in caution. Cloud is built so you can hold it in your head: four things, in one order.
- Organisation
- Project
- Products switched on
- Credential
A key calls only what's on
A credential belongs to a project. A project switches products on and off. A key can only call what its project has switched on.
Off means off
Disable a service and every credential that reached it stops. Now, not eventually.
Billed by what you actually use
Requests are counted where they arrive and priced where you can see them, on the usage page. The bill is the usage page with a date on it.
Free before you decide
Test credentials are free the moment you sign in. No card, no sales call. Make a request before you've decided whether you like us.
Login with Roola
The sign-in form you don't have to build.
Let people sign in with the account they already have. One button, one redirect. You never see a password, so you never store one, so there's nothing to leak.
- Register a client in the console and put the button on your site.
- Use it on its own. You don't need any other product switched on.
- It's the same door every Roola product signs its own users in through. We don't have a better one for ourselves.
- 1 Your siteSomeone presses the button.
- 2 Roola AccountsThey sign in there — the only place a password is ever checked.
- 3 Back to you, with a codeYou exchange it for a token.
- 4 Their profileYou read it with the token. No password ever reached you.
Sign in with RoolaOpening soon · for builders
Sign in. Get a key. Make a request. Then decide.
We have no users yet — we're saying so cheerfully. Leave an address and your keys will be ready when the console opens. Cloud is an organisation's product: one Roola account, one organisation, seats for the team.
One email when we open. Nothing else, ever.