Who runs what, in whose account.
Running inside your cloud account doesn't make the software run itself. This page sets out what gets deployed, who owns each routine task, and which event stores work today.
Deployment models
| Model | Where it runs | Status |
|---|---|---|
| Customer cloud | DepSmith components in your cloud account, reading your event store in place | Offered |
| Hosted | Being defined — either in our cloud, or operated for you in yours. Where the data sits differs between the two. | Being defined |
Responsibilities in the customer-cloud model
The split below is our proposed default, which we agree with each design partner before go-live. Open: whether DepSmith has any remote access for upgrades or support. If it does, we'll document how access is granted, approved, logged and revoked here before it is used.
| Task | You | DepSmith |
|---|---|---|
| Cloud account, networking, IAM roles | Own and approve | Provide the least-privilege policy and network requirements |
| Warehouse read access | Grant and revoke | Specify the minimum grants |
| Compute capacity and its cost | Pay your cloud provider | Publish sizing guidance and expected query load |
| Installation | Approve and run, or let us run with temporary access | Provide the package and walk you through it |
| Upgrades | Approve the change window | Ship releases with notes; open: who applies them |
| Backups of DepSmith state (catalog, saved reports) | Open | Open |
| Monitoring and alerts | Your platform alerts | Open: what health signals we see |
| Incidents | First response for your infrastructure | Response for application defects; open: response targets |
| Removal | Delete the deployment and revoke access | Provide the removal checklist (see exit) |
Supported event stores
"Live" means supported in the current release. "On request" means we scope it with you, it may need custom work, and we'll tell you the timeline before you commit.
| Store | Status | Notes |
|---|---|---|
| ClickHouse | Live | Open: supported versions and schema assumptions — ask us |
| Snowflake | On request | Scoped per customer |
| Databricks | On request | Scoped per customer |
| BigQuery | On request | Scoped per customer |
| Redshift | On request | Scoped per customer |
| Postgres | On request | Scoped per customer; fit depends on event volume |
| S3 | On request | Object storage isn't a query interface on its own — it needs a query engine in front, or an ingestion path into a supported store |
If your events don't land anywhere you control yet, there is a collection path that gets them there first. Which one depends on your stack.
Before a working session on your own data
- Your security review of this page and the Security page.
- A read-only role on the event store, approved on your side.
- Someone who knows your events, and an analyst who can approve definitions.
- Two or three real questions you already know the answer to, so the first results can be reconciled.
Questions this page doesn't answer are the ones we want to hear. Ask on a call, or write to contact@depsmith.com.
Request a demo