Kinesis Private · for security, privacy and sovereignty
Your own Kinesis Grid, just for you, or in your own data center.
Isolated: your own Kinesis deployment, run by Kinesis and sealed off from every other customer. Fully private: all of Kinesis runs in your own data center, operated by your team, and Kinesis is not in the loop. At both levels, your work runs on your own servers.
Kinesis Grid, our hosted service, is free to start: no Grid fee on your first 5 servers, and your first 5 users are free. Kinesis Private is quoted per deployment.
Why private
Your security team said no to a shared, hosted control plane.
They had good reason. But the choice then looked like years of building GPU sharing in-house, or expensive hardware sitting idle. Kinesis Private removes that choice: the same platform, run as privately as your rules require.
Control plane
- Scheduling
- Users and roles
- Audit trail
Data plane
- GPU servers
- Workloads
- Data and models
Fully private: both planes inside your walls
Choose your level
Choose where the control plane runs.
The control plane is the part of Kinesis that schedules work and keeps your settings, users and logs; the data plane is the servers your work runs on. Your servers and data stay yours at every level: the difference is where the control plane runs, and who runs it.
| Kinesis Grid | Isolated | Fully private | |
|---|---|---|---|
| Control plane | Hosted by Kinesis | A dedicated deployment, run by Kinesis | In your data center, run by your team |
| Data plane | Your servers, secured and private | Your servers, secured and private | Your servers, secured and private |
| Separation | Your own organization and Grids | Sealed off from every other customer | Complete: Kinesis is not in the loop |
| Who runs updates | Kinesis | Kinesis | Your team |
| Best for | Most teams, and the fastest start | Regulated teams that want a managed service | Sovereign, classified and strictly regulated environments |
Kinesis Grid is the hosted service most teams start on. Kinesis Private comes in the two levels on the right.
Security
What your security review will look for.
The controls your auditors expect, built in rather than bolted on, and every action with a name on it.
- Single sign-on through Okta, Microsoft Entra or Google Workspace, and admins can require it for everyone
- Org roles (Admin, Developer, Viewer) and Grid Users and Editors
- Multi-factor authentication (MFA)
- An audit trail of every change: who, what and when
- Billing per organization: its own balance, payment methods and invoices
- Private connectivity to every machine. No inbound ports, unless an app must accept connections
- Your Grid never places work on community hardware unless you choose Kinesis Batches
- 09:14ana · Updated grid quotaslab-a100
- 09:02ben · Fair share scheduling updatedlab-a100
- 08:47dana · Invited a member as Developerrisk-team
- 08:31dana · Deployed an apprisk-model-v3
- 08:05chen · Turned on two-factor authenticationchen@risk-team
Illustrative
Nothing held back
The same platform, wherever it runs.
The full platform
Fair share, quotas, GPU slicing, orchestration, and usage and cost by project and app. The same features as Kinesis Grid.
Federated across your estate
Data centers, labs and the cloud accounts you own, under one private control plane.
Sovereign by design
Data and workloads stay on your servers at every level. With Fully private, the control plane and its telemetry stay with you too.
The same Kinesis at every level
Start on Kinesis Grid, move to Isolated or Fully private, and your teams never relearn a thing.
How it goes
From first call to running workloads.
A private deployment is a project we run with your team, not a box we ship.
- 1
Map your requirements
Where it must run, who may operate it, and which regulations apply. That decides Isolated or Fully private.
- 2
Deploy the control plane
Kinesis sets it up in a dedicated environment or in your data center, together with your team.
- 3
Connect your estate
Servers in your data centers, labs and cloud accounts join with one install command each.
- 4
Hand it to your teams
Grids, quotas and roles in place, and your developers deploy the same way they would on Kinesis Grid.
Who it’s for
When private is a requirement, not a preference.
Best fit
- Banks and insurers
- Hospitals and life sciences
- Defense and the public sector
- National and sovereign AI clouds
- University consortia
- Any enterprise whose security team won’t approve a third-party control plane
Not a fit
- Teams that are happy on a hosted control plane: Kinesis Grid gets you running faster.
Tell us what your environment needs.
Where it must run, who may operate it, and which rules apply. We will map out the deployment with your team, and tell you if Kinesis Grid would serve you just as well.