Intent agent
Turns “we need a Postgres for payments, highly available, backups kept six months” into a structured request.
Not another cloud provider. Every server, database and cluster comes with AI agents that provision, patch, heal and scale it around the clock — under a control plane that never lets them act alone.
Global clouds hand you building blocks and a bill for the people to run them. hiveSRE Cloud ships with the people already replaced by software you can audit.
A few specialised agents, each with one narrow job — and one piece of ordinary software that holds all the authority. A hive of workers, one keeper.
Turns “we need a Postgres for payments, highly available, backups kept six months” into a structured request.
Works out exact sizes, versions and steps, with its reasoning attached, and opens a pull request a person merges.
Watches everything running. When something breaks it explains what happened and asks for a permitted action or writes up a fix.
Deterministic software, and the only part of the system that can actually change your infrastructure. Agents hand it proposals; it decides whether they are safe to apply.
No tickets, no runbooks, no console clicking. Every step after your request produces a signed record.
In plain language through the Intent agent, or by editing a small file.
Concrete sizes, versions and steps, opened as a pull request with the reasoning.
Later, routine changes can be merged by policy.
Snapshot if needed, apply, and wait until the result is healthy.
Around the clock, with no dashboards for your team to stare at.
Diagnosed, fixed through a permitted action or a new proposal — back through the same loop.
Most “AI for ops” hands a model the keys and hopes. That's fine for a demo and unacceptable for a bank. hiveSRE is built the other way round: agents propose, the control plane acts.
No agent can create, change or delete infrastructure. Only the control plane can, and only after its checks pass.
Deleting data or downsizing waits for a named human. A snapshot is taken first.
Agents work from structured intent and produce structured, reviewable changes.
Agents use models on your own hardware. No hosted AI APIs, no telemetry, no call-outs.
Every change and every emergency action produces a record like this: what the agent saw, what it proposed, which policy allowed it, who approved it and what was done. Logs can be edited. These can't — and anyone can verify them offline.
The building blocks you'd expect from a cloud — each one operated by the agents from day one. Some are still on the roadmap; ask us which.
Virtual machines on fast local storage, right-sized and patched by agents.
High availability, point-in-time restore and replicas. The Operator handles failover.
Managed clusters with upgrades and node health handled for you.
S3-compatible buckets, with retention locks where you need them.
Private networks, firewalls and load balancers, kept in line with your policy.
Private language models, including Hebrew-capable ones, that never send data outside.
Isolated micro-VMs for running your own AI agents safely.
Private hosting for the files that describe your infrastructure. Rollback is usually one revert.
Signed records for every operation on your account. Always on.
Operations are included in every option, so there's no ops headcount on top. Nothing inside calls out to the internet — the agents use models running on the same hardware.
A ready-made cloud with the agents already running it. Start in days.
Your servers, in your data center or colo cage. Our control plane and agents run them.
No internet at all, and the agents still run everything.
A regular cloud rents you the parts and leaves running them to you. hiveSRE Cloud includes the operations team: AI agents that provision, patch, heal and scale your services around the clock, under a control plane that checks every change.
No. Agents can only propose. The control plane — ordinary, deterministic software, not an AI — is the only thing allowed to change infrastructure, and only after its checks pass. Anything destructive waits for a named person.
A bad proposal fails the control plane's checks or is rejected in review. Snapshots are taken before anything that can't be undone, and because every change lives in git, rolling back is usually a single revert.
Far less of one. Provisioning, patching, failover, tuning and 3am pages are handled by the platform. Your engineers decide what the platform should be and approve anything risky.
No. It works from structured intent and produces structured, reviewable changes. Free text is read, but never executed.
Hosted in Israel, on your own hardware, or fully air-gapped. The agents use models running inside that environment; nothing calls out to the internet.
A signed evidence record for every change: what the agent saw, what it proposed, which policy allowed it, who approved it and what was done. It can be verified offline, without access to our systems.
We're onboarding a small number of design partners who will shape the roadmap and work directly with the founding team. Tell us what you'd like the agents to take off your plate.
Prefer email? [email protected]