Enterprise

Enterprise security for agents
‍acting on customer data.

Your agents hold credentials to your customers’ systems and act inside them. Scalekit ships that access with the deployment options, certifications, access governance and evidence an enterprise review asks for.

Talk to an engineer

EXPLORE TRUST CENTER

Four deployment models.
Same product in all four.

The gateway, SDKs and connector catalogue never change. You choose where it runs, who holds the keys and who controls upgrades.

Managed cloud

Multi-tenant with per-tenant encryption, in a US or EU region. Nothing to operate, residency enforced at the storage layer.

Your VPC

Runs inside your own AWS, GCP or Azure account. Customer data never leaves your cloud, and connector egress originates from your network.

Customer infrastructure

Deployed into your customer's environment, fully isolated. One instance per customer, with keys and upgrade cadence under your control.

Air-gapped

No outbound calls to Scalekit. Offline licence validation and images from your own registry, for classified and disconnected networks.

If it's air-gapped,
‍it's actually air-gapped.

Private deployment is a contractual commitment, not a configuration flag. In an air-gapped install, no data, logs, metrics or telemetry reach Scalekit infrastructure.

Read the guide

Guarantee 1

No data leaves your deployment

Credentials, OAuth tokens, session data and user records are stored and processed entirely within your deployment. No Scalekit server sits in the data path.

Guarantee 2

No telemetry by default

Usage metrics stay in your observability stack, not ours. There is no default outbound metrics channel to discover and disable.

Guarantee 3

Logs are optional and configurable

You decide whether any logs are exposed to Scalekit for support. The default configuration grants no log access.

Guarantee 4

Not a sub-processor

With no Scalekit component in the data path, we do not process your customer data and are not a sub-processor for that deployment.

Certifications, controls,
and what happens to data.

What we're certified for, how we handle data, and the documents that prove it.

Compliance frameworks

SOC 2 Type II, HIPAA and GDPR. We sign a BAA, and a DPA with SCCs.

Encryption

AES-256-GCM at rest and TLS 1.3 in transit. Credentials can be wrapped again with your own key.

Data residency

Data stays in the US or EU region you choose, enforced at the storage layer. Private deployments can run anywhere.

Retention and deletion

Retention is set per environment. Deleting an account removes its credentials and call history.

Sub-processors

Every sub-processor is in a public register, with notice before material changes. Private deployments use none.

Defense in depth

Segregated networks, unique credentials per person and service, and least-privilege access that is logged and reviewed.

Penetration testing

An annual third-party pen test with tracked fixes, plus continuous automated scanning.

Vulnerability disclosure

A direct channel to our security team, with acknowledgement on a set timeline.

Every certification,
‍on request.

A security review starts with a document request. Rather than routing it through your account team, request what you need directly and receive it under NDA where required.

SOC 2 Type II

Penetration test summary

DPA & SCCs

HIPAA BAA

Security questionnaire

Sub-processor register

Architecture documentation

Visit the trust center

Credentials never touch your agent. Keys never touch us.

Tokens live in an encrypted vault and are attached at call time. The key that protects the vault can stay in your own KMS.

Isolated token vault

Encrypted per tenant. Never in your code, logs or prompts.

At rest

AES-256-GCM

, per-tenant data key

In transit

TLS 1.3

to every connector

Injection

Attached by the gateway at call time

Bring your own KMS

Your key, in your KMS. Revoke it and stored tokens are unreadable.

Supported

Grant

Encrypt and decrypt operations only

Key material

Never transmitted to Scalekit

Govern who can change what.
And keep the record.

Control who in your organisation uses the dashboard, what they can change, and keep a record of it.

Talk to an engineer

SAML single sign-on

Dashboard access through your own identity provider, with your organisation's session and MFA policies enforced.

SCIM provisioning

Users and groups provisioned and deprovisioned automatically from your directory. Access ends when employment does.

Role-based access control

Restrict what each user can view and change by assigned role, so connector configuration and production credentials are not open to everyone.

Admin audit trail

Full accountability for every action taken in the dashboard — who changed a connector, rotated a key or altered a role, and when.

Scoped API credentials

Separate keys per environment and per team, independently revocable, so a compromised development key never reaches production.

IP allowlisting

Restrict gateway and dashboard access to your own network ranges, alongside the per-call authorization model.

A forward-deployed engineer, not a ticket queue.

Enterprise deployments come with a named engineer who knows your architecture, joins your security review, and stays with the account after it goes live.

Named engineer

One person accountable for your deployment, from architecture review through to production and upgrades.

Expert-led answers

Your security questionnaire comes back filled in by the team that built the system, not paraphrased from a help centre.

Architecture review

A working session on your deployment topology, network boundaries and residency constraints before signing.

Named escalation path

A defined route and response commitment for production incidents, agreed in the contract rather than discovered during one.

Pre-sales
Technical questions

Does a private deployment require outbound internet access?

Not in air-gapped mode. In VPC and customer deployments, traffic goes out only to the connectors your agents call.

What does it run on?

Containers on Kubernetes, with Helm charts, on AWS, GCP, Azure or bare metal.

How is data retained and deleted?

Retention is configurable. Data is deleted on termination within a contracted window.

Can we license one isolated instance per customer?

Yes. Each instance is isolated and upgraded on its own.

Who owns the credential when an agent chains multiple tools?

The user who authorized it, for every call in the chain.

Is Scalekit a sub-processor?

Not on-prem. In managed cloud, yes, and the register is in the Trust Center.

Enterprise security for agents‍acting on customer data.

Four deployment models. Same product in all four.

If it's air-gapped,‍it's actually air-gapped.

Certifications, controls, and what happens to data.

Every certification,‍on request.

Credentials never touch your agent. Keys never touch us.

Govern who can change what. And keep the record.

A forward-deployed engineer, not a ticket queue.

Pre-sales Technical questions

Start the security review.We will meet it.