Infrastructure platform · Private preview
Your infrastructure. One platform.
Build, host, and operate your applications, data, domains, and email—with local AI agents that observe, act, and verify.
osact is bringing the essential services behind your business into one control plane, built around infrastructure you control and operations you can inspect.
- Observe
- Diagnose
- Plan
- Act
- Verify
Platform
One platform for the services you need.
Bring your services together. Keep their operation connected. Each area below shows where it stands today.
-
Applications and compute
Deploy applications and APIs with configuration, secrets, health checks, logs, release history, rollback, and usage visibility. Isolated execution is part of the hosting architecture.
Private preview
-
Data and storage
Connect applications to databases, object storage, key-value storage, cache, and durable queues, with scoped access and explicit recovery paths.
Private preview
-
Domains and DNS
Manage domains, authoritative DNS, DNSSEC, and application routing. Our own registrar operation is in development; it depends on registry onboarding, so domain registration is not offered today.
DNS in private preview · registrar in development
-
Email
Bring business mailboxes and application email into the platform, with domain authentication, delivery records, and operational controls. Public delivery is qualified separately from private testing.
Private testing · public delivery awaits qualification
-
Network and access
Connect services through HTTPS routes, access policies, private connectivity, and request controls.
Private preview
-
AI and automation
Combine local inference, agents, schedules, and durable workflows with the same project permissions and service state.
Private preview · autonomy under qualification
- Running in private preview
- Partly in development
- Awaits outside qualification
How it works
Agents that work toward an outcome.
Give an agent a scoped objective. It reads the relevant service state, chooses from authorized tools, and checks what changed. Operations retain their history so a proposal, an attempted action, and a verified result remain distinguishable.
AI helps decide. Permissions, secrets, accounting, and execution boundaries stay enforced by software.
Observe
Read current service health and relevant operational facts.
Diagnose
Distinguish a known failure from missing or uncertain evidence.
Plan
Select a permitted workflow or revise the approach as evidence changes.
Act
Execute through typed tools and deterministic permission checks.
Verify
Independently check whether the requested outcome was achieved.
- ObservedThe condition is recorded.
The platform records what it observed about the application.
- ProposedA permitted workflow is chosen.
The agent selects a recovery workflow it is authorized to run.
- AttemptedThe recovery workflow runs.
Execution passes through the same permission checks as any other action.
- Verified, or unresolvedA fresh health check decides.
It confirms recovery, or keeps the outcome unresolved.
This explains the operating model. It is not a promise that every incident is handled autonomously.
Local AI
Intelligence close to your infrastructure.
osact is designed around small models running locally for interpretation, diagnosis, and tool selection. Everyday infrastructure functions do not need a language-model decision for each request.
Every request
No model sits in the path of an ordinary request.
Operational judgment
A model proposes. Software checks permissions and carries out the action.
- Control
Greater control over where operational inference runs.
- Separation
AI decisions stay separate from critical execution rules.
- Improvement
A path to platform-specific improvement using permissioned, privacy-filtered operational evidence.
Control
Infrastructure you can understand and move.
Designed for portability, with private deployment as a central goal. Supported configurations are discussed during early access.
- 01
One workspace
Projects, service configuration, access, and activity in a consistent interface.
- 02
Inspectable operations
Durable records of actions, outcomes, and uncertainty.
- 03
Recovery as part of the platform
Backups, restoration, deployment history, and rollback with explicit data semantics.
- 04
Private deployment
A path to operating the platform on infrastructure controlled by your organization.
Developer journey
From application to operated service.
The intended path through the platform, from a new project to a service that is watched and managed.
- Step 1
Create a project
One place for its services, access, and activity.
- Step 2
Deploy an application
Release it with configuration, secrets, and health checks.
- Step 3
Connect data and a domain
Attach storage and route a domain to the application.
- Step 4
Add operational workflows
Give agents scoped objectives and the workflows they may run.
- Step 5
Observe and manage the result
Read what happened, what was attempted, and what was verified.
Availability
Help shape the next infrastructure platform.
osact is in active development, with private platform capabilities being built and verified on our own infrastructure. We are preparing the next stages of service availability and private deployment.
Request early access
For developers and teams interested in trying the platform.
Discuss a private deployment
For organizations with specific hosting and infrastructure requirements.
FAQ
Questions, answered plainly.
What is osact?
A unified infrastructure platform being built for hosting applications, managing services, and operating them with local AI agents and deterministic controls.
Is it an AI hosting product or an infrastructure platform?
It is an infrastructure platform with an agentic operations layer. Customer AI workloads are also part of the intended catalog.
Does AI handle every request?
No. Core services run through conventional software. Models are used where interpretation, diagnosis, or planning adds value.
Can I run it on my own infrastructure?
Private operation and portability are central design goals. Deployment suitability and supported configurations are discussed during early access.
Can I register domains and send email today?
Public availability depends on the service. Own-registrar operation and external email qualification require additional onboarding and infrastructure, so neither should be assumed to be generally available. The platform section above shows where each service stands.
Is it a drop-in Cloudflare replacement?
No, and we do not promise one. The goal is a broad independent platform. Existing applications need a compatibility review and a migration plan for the products, bindings, and data they use.