Atrium Tell us what to build
LiveKitefield opened a tutoring product in 3 minutes. Watch it open

Describe your product.Your customers use it minutes later.

A working product on your own domain, under your own name. Customers sign in, talk to an assistant that gets things done, and watch the work happen.

Tell us what to build
 
Open in 0:00

What should your customers be able to do?

Open it

Conversation

Ask anything
✓

Each tab is a different company's product. Their name, their domain, their words. Kitefield's is in production today.

The demo is where other tools stop. It is where this one starts.

App builders hand you screens. Everything a paying customer needs arrives with the portal, already running.

An app builder gives youAtrium opens with
Sign-inA login screenReal accounts by email or Google, per customer
The assistantA chat mock-upStreams answers, takes files and voice, acts on requests
Work that runsA spinnerJobs that run in the background and report back
Domain and uptimeYour problemYour domain, a certificate, and someone watching it
CostA surprise invoiceWhat each customer costs you, per month, in money
Whose name is on itTheirs, in the footerYours, everywhere, and only yours

Pick what it can do. Watch your portal grow.

Every capability is a finished piece. Switch one on and it appears in your customers' portal, working, in the place they would expect it.

Blocks
Hover a block to find it in the portal

Your customers never meet your supplier.

Every answer passes through a vocabulary map before it leaves. Internal identifiers are sealed, internal hostnames never appear, and error messages are written in your voice rather than forwarded.

What happens underneath
What your customer reads
Enforced by the build

The code that writes a response cannot import the code that knows internal names.

Checked on every response

A final scan redacts anything that slipped past the map, and the test suite fails.

No links out

Not in the app, not in an email, not in an error. Every path is on your host.

Three moves to open the doors.

Most portals open the same week as the first call. Nothing about your product is built from scratch, so there is nothing to wait for.

1Day one, 30 minutes
2The same afternoon
3When you are ready
Call with AtriumYou and one of us
12:40
You: Our clients keep emailing to ask where their case is. We want them to just ask, and see it.

1Day one, 30 minutes

Say what it does

Who your customers are and what they come to get done. For now that is a conversation with us; self-serve is next.

Conversation
Files
Notifications
Your colour

2The same afternoon

Choose the blocks

Pick from the catalogue, set your name, colours and voice. You see a working version on a test address.

TypeNamePoints toCNAMEhelpthe address we send you
Record found
Certificate issued
Open on help.yourcompany.com
Live

3When you are ready

Point your domain at it

One DNS record. Every request after that runs with a credential scoped to one customer.

Built for three kinds of team.

If your customers should be able to sign in, ask for something and see it get done, it fits.

You prototyped it, and it stalled.

The assistant works in a notebook. Accounts, billing, a domain and a support inbox are three months you do not have. Keep the idea, skip the plumbing.

You build for clients.

Agencies and integrators open one portal per client, each on the client's own domain, each billed and measured separately.

You have a product, and want an assistant in it.

Put a working assistant in front of your existing customers without rebuilding what you already have.

Tell us what your customers should be able to do.

We stand up a first version on your host. You try it with a real customer before you decide anything.

A person replies within one working day.