How agentdbaas works
We hold the cloud account, stand up the backend, and hand your agents scoped credentials.
Agent Flight Recorder
Know exactly what your agents did
The tape is the system of record for what your agents did. We record every session, tool call, model turn, and cron beat against the agent that made it. The record is sequenced, timestamped, and append-only.
What the tape holds
Every event, against the agent that made it
We record four kinds of event. We record each one against the agent that made it. We keep them in order.
- A session. Each run an agent opens from start to stop.
- A tool call. Each call an agent makes to a tool, with the tool output it got back.
- A model turn. Each turn the agent takes with the model.
- A cron beat. Each scheduled run on the clock.
We stamp each event with a time and a sequence number. So the tape reads in the order the work ran. You can trace one agent from the first event to the last. The record is append-only, so no event moves once we write it. We record the cost and the tokens of each event too. So the tape carries the price of the work next to the work.
Encryption
We hold the tape. You hold the key.
We encrypt prompts, messages, and tool output before they leave the host. The backend stores ciphertext. It has no private key. You hold the decrypt key, so we cannot read your prompts or your tool output. Event metadata stays visible without the key. You can see the id, the time, the type, the cost, the tokens, and the sequence of every event while the content stays sealed.
What a gap means
A gap in the tape is a finding
We leave the raw record alone, so the tape shows the work as it ran. When a run stops before the last event, the tape shows the space where the next event would sit. A gap is itself a finding. It marks where the work stopped and it tells you where to look. A clean tape and a tape with a gap are both answers.
What you do with it
Replay a bad run and find the call that broke it
When a run fails, you replay it. You follow the sequence from the first event to the last, read each tool call and model turn in the order it ran, and find the call that broke the run. The tape is the raw record, so you see the real work in full: the call, the time it ran, and the sequence around it.
Demonstration
SKYWARD-7 · event metadata
Content sealed
| Seq | Time | Type | Cost | Tokens |
|---|---|---|---|---|
| 0041 | 03:02:11 | session | none | none |
| 0042 | 03:02:12 | model turn | $0.004 | 1,180 |
| 0043 | 03:02:14 | tool call | $0.000 | 96 |
| 0044 | 03:02:15 | cron beat | $0.000 | 0 |
Next
See how the backend runs
What it costs to run it
Three tiers. One unified backend in each.