Thalamus investigates your incidents, finds the cause, and proposes the fix — in your own instance, in the region you choose. Provisioned in minutes, not a quarter of procurement.
No card required to start. Annual contracts, invoiced on net terms.
The deployment packs are already built and tested against live accounts in all three major clouds. Provisioning runs them; it does not invent anything on the day.
Email, password, confirm the address. No sales call to get in.
about a minute
Your instance lives at yourname.tenant.thalamusaicloud.com, in the
region closest to the systems you are monitoring.
Infrastructure, database, hardened defaults, DNS. You watch the actual steps — not a spinner — and we email you when it is ready.
a few minutesPoint it at your monitoring and your repositories. The fleet starts watching what you onboard, and nothing else.
the same afternoonDashboards tell you something broke. Thalamus works out why, writes it down, and proposes the change — with the evidence attached.
Correlates signals across monitoring, logs, traces and recent changes, then says what it thinks caused the incident and how confident it is.
Proposes a fix as a pull request against your repository, with the test that demonstrates it. You review and merge — or do not.
Every claim is labelled as fact, observation, inference or hypothesis. You can tell what was measured from what was guessed.
Redaction, retention and subject-rights handling are built in, not a later module. Credentials are encrypted at rest with your own key.
Observe, recommend, approve — then more if you want it. The fleet does not act beyond the level you set, and the level is yours to move.
AWS, Azure or GCP. Data residency is a dropdown at signup, not a professional services engagement.
Not per seat, not per host, not per gigabyte ingested. A service is a production thing you want the fleet to watch and act on — its own deployment, its own golden signals, its own on-call expectation. Not every repository, and not every container.
Launch, Team and Division run on shared infrastructure. Your data is stored in a shared database, separated from other customers by enforced database-level access controls, and is never accessible to another customer. Your monitoring, credentials and incident history remain private to your organisation.
Enterprise runs in an AWS account created for your organisation, with its own database. No infrastructure is shared with any other customer, and you choose the region.
Crossing a tier does not generate a charge and does not stop anything. We do not take the fleet off a service because a counter moved.
Your console shows peak usage and what it means for renewal, throughout the term. A true-up should never be the first you hear of it.
A production service you want the fleet to watch and act on — typically something with its own deployment, its own golden signals and its own on-call expectation. Not every repository, and not every container. Only services you have actually finished onboarding are counted; a half-configured one is not billed.
Minutes, not days. The deployment packs are already built and tested against live accounts, so provisioning runs something that works rather than assembling it on the day. If it fails, we roll back and tell you — and nothing is charged for an instance that never came up.
Yes, on Enterprise. Your instance runs in an account created for your organisation with its own database, and nothing is shared with another customer. For running entirely inside infrastructure you already own, that is our managed service rather than this product — worth a conversation about which fits.
You can export it at any time, and we delete it on request. Suspension for a late invoice does not delete anything — your data is retained and comes back when the payment clears.
You choose what to connect. Credentials are encrypted at rest with a key held by your instance, and the fleet operates at the autonomy level you set — starting at observe-and-recommend, where it changes nothing.
You can create an account and see the console without paying. Provisioning a real instance creates real infrastructure, so that starts a contract — talk to us and we will scope it against your actual estate first.
A 45-minute look at how your estate actually runs — incident volume, MTTR, what recurs, where the hours go. If there is not enough repetitive volume to justify going further, we will say so.