DocsExplanation
How the service is built
A small number of parts, each with one job, kept separate so a page cannot leak a service key.
By the Callaroo team. Updated November 2026
Callaroo is a web dashboard, a server that handles workspace requests, and a call service that handles live calls. A database keeps the business records. A few outside services provide the phone line, the voice, the payment and the file storage. This page explains how those parts fit together.
Swipe the diagram sideways to see the full flow.
The browser, the dashboard server, the database and the outside services are separate layers. The server is the only layer that holds service keys.
The stack
| Layer | Built with | Job |
|---|---|---|
| Dashboard | Next.js, React and TypeScript | Shows the workspace and sends signed-in requests. |
| Server | Next.js route handlers and a TypeScript service | Checks access, validates input and coordinates work. |
| Database | Supabase Postgres | Stores workspaces, menus, calls, orders and bookings. |
| Files | Supabase Storage or private object storage | Holds call recordings when storage is configured. |
| Calls and texts | Telnyx | Provides the number, carries calls and delivers messages. |
| Voice | Grok Voice | Runs the live speech and language call. |
| Billing | Stripe | Handles the plan, card and invoices. |
The dashboard and the call service use the same workspace records. A call is written under the workspace that owns the number, and the dashboard reads it through a signed-in membership. The browser never receives the phone company key or the voice service key.
The dashboard
- The owner or manager signs in and chooses a workspace.
- The page asks the server for records that belong to that workspace.
- The server checks the membership and returns only what the role allows.
- The page renders the menu, orders, calls, messages, billing or settings.
The call path
A caller dials the business number.
The phone company sends the call to the Callaroo voice service.
The voice service opens a live call and loads the saved workspace settings.
The assistant speaks, listens and asks a tool when it needs a saved fact.
The tool reads or writes a workspace record and returns the result.
When the call ends, the transcript, summary, outcome and minutes are saved.
How records stay separate
Every business record carries a workspace code. The database checks that code against the signed-in member before it returns a record. A page cannot widen that boundary by asking for another workspace. A staff tool uses the same check, so a caller and a member of another workspace fail in the same way.
Why the parts are separate
- A page bug cannot hand out a phone company key, because the key never reaches the browser.
- A call can keep working while a dashboard page is slow, because the voice path does not render a page.
- Billing can fail without deleting the menu or the call record.
- A recording can be missing while the transcript remains readable.
What this page does not cover
- Deployment details, private network layout and internal project names.
- Secrets, keys or account identifiers.
- A promise that every service is always available.
- Features that are planned but not shipped.
Read Security and access for the controls that protect a workspace, and What connects to Callaroo for the outside services.