Cloud and the hardware you already own, one control plane
Most platforms treat on-premise as a special case bolted onto a cloud-first product. Sencai works the other way round. The fleet agent behaves the same on a cloud instance and on a server in your own rack, and enrollment never asks whether a machine has a cloud account. Owned hardware, cloud capacity or both: the same control plane, audit trail and runbooks apply everywhere.
The same agent on every Linux box
Install the fleet agent on a cloud instance or a physical machine and it behaves the same. Monitoring, patch management, software inventory and runbook automation all run through one agent, with the same approval gate before anything executes. Write a runbook once and run it against a Scaleway VM today and a colocated bare-metal box next week. A separate agent handles Kubernetes: install it in-cluster and manage that cluster from the same dashboard. There is one download and one install process, whether you roll it out across cloud instances or a few servers under a desk.
No cloud account required
Enrolling a server does not require a cloud provider account, because much on-premise hardware has none. A rack server, a colocated box or an old workstation used as a build machine enrolls directly, with no cloud credential in the process. Afterwards, cloud instances and standalone hardware share one fleet view: filterable, taggable and managed through the same screens and runbooks. If your estate is entirely on-premise, the agent, audit log, patching and runbooks work exactly as they do for a cloud-only team.
Cloud accounts connect, nothing migrates
For the cloud side, Sencai connects to accounts you already have across eleven providers: Hetzner, OVHcloud, Scaleway, UpCloud, AWS, Azure, Google Cloud, DigitalOcean, Vultr, Akamai/Linode and Oracle Cloud. The account, contract and invoice stay with the provider. Sencai holds an encrypted credential, and you can revoke it at the provider at any moment. Instances, networks, storage volumes and DNS zones appear in inventory automatically. You then decide, resource by resource, what comes under active management. See Hetzner for what a connected provider supports today. Sencai can also provision and bill capacity under its own accounts if you prefer one contract; both models sit in the same inventory.
One inventory, one policy
Cloud instances, on-premise servers and Kubernetes clusters land in the same inventory. They share role-based access control, single sign-on through Microsoft Entra ID or Google Workspace with SCIM provisioning, and the same just-in-time elevation workflow for temporary access with an approval attached. An access audit gets the same answer for a colocated server as for a cloud instance. See security and compliance for how that access model holds up under review.
One audit trail, and an on-premise edition
Every action across the fleet, cloud or on-premise, writes to the same append-only, hash-chained audit log. Sencai does not hold ISO 27001 or SOC 2 certification and says so. For reviewers it provides an exportable audit trail, records of processing, a sub-processor register, a data-residency statement and a published Data Processing Agreement. For critical and strategic systems there is also Sencai On-Prem: an annual licence with support included, delivered as a complete server with hardware, software and installation, optionally with a local AI server that automates the platform entirely on-site.
Bring the hardware you already have
Connect an account or enrol a server: both land in the same inventory, with nothing to migrate. The free organisation covers one user and five managed resources with no card and no time limit. Beyond that you pay per resource and per person; see [pricing](/pricing/).