Draft — under review. Last updated 19 October 2026. Where a fact is still open, this page says so rather than guessing.
Deployment

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

ModelWhere it runsStatus
Customer cloudDepSmith components in your cloud account, reading your event store in placeOffered
HostedBeing 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.

TaskYouDepSmith
Cloud account, networking, IAM rolesOwn and approveProvide the least-privilege policy and network requirements
Warehouse read accessGrant and revokeSpecify the minimum grants
Compute capacity and its costPay your cloud providerPublish sizing guidance and expected query load
InstallationApprove and run, or let us run with temporary accessProvide the package and walk you through it
UpgradesApprove the change windowShip releases with notes; open: who applies them
Backups of DepSmith state (catalog, saved reports)OpenOpen
Monitoring and alertsYour platform alertsOpen: what health signals we see
IncidentsFirst response for your infrastructureResponse for application defects; open: response targets
RemovalDelete the deployment and revoke accessProvide 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.

StoreStatusNotes
ClickHouseLiveOpen: supported versions and schema assumptions — ask us
SnowflakeOn requestScoped per customer
DatabricksOn requestScoped per customer
BigQueryOn requestScoped per customer
RedshiftOn requestScoped per customer
PostgresOn requestScoped per customer; fit depends on event volume
S3On requestObject 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