One platform. Many bots. Your data, your tenancy.

Where your bot actually runs.

Three options. The first thing each one answers is where your data sits, because that is the question that actually matters.

Shared Platform Where data lives: your own Postgres schema on CoreShift infrastructure, in AWS US regions. You own: your data, your configuration, your integration credentials, and a full export whenever you ask. CoreShift owns: the hosts, the database, the platform code, patching, backups and monitoring. This is the default, and it is what every bot runs on today.

Private Tenant Where data lives: a dedicated database and dedicated compute, still operated by CoreShift. You own: the same as above, plus isolation that does not share a database instance with anyone else. CoreShift owns: the same operational responsibility as Shared Platform. For workflows where "your own schema" is not a strong enough answer — finance, legal, anything with a compliance reviewer asking the question. Pilot customers may choose Private Tenant at no uplift for the pilot period.

Client-Hosted — on request Where data lives: on your infrastructure. It never leaves. You own: the machine, the database, the network, and the operational burden that comes with them. CoreShift owns: the packaged bot, its updates, and the runtime that loads and runs it — including a hash-chained audit log that is verifiable independently of the bot's own records.

This one is on request rather than off the shelf. The runtime exists and has been run end to end — a packaged bot loaded from its archive, migrations applied, a human-gated state change performed, and the audit chain verified by tampering with a copy and watching it fail at the altered line. No customer runs it yet, and we would rather tell you that than sell you a first. Ask, and we will scope it with you.

No prices on this page. See pricing