Develop in cloud. Deploy on-site. Operate centrally.
Nebulix gives infrastructure teams one operating hub for workloads that start in managed cloud clusters and move to on-site appliances when data locality, latency, sovereignty, or operational constraints require local compute.
Start in cloud while your physical appliance is prepared. Deploy the same workloads on-site when the hardware arrives.
Prefer email? Contact info@nebulix.cloud.
$ nebctl get sites
NAME TYPE STATUS ENV
cloud-dev-01 virtual Ready development
cloud-stage-01 virtual Ready staging
factory-de-01 physical Preparing on-site
$ nebctl deploy workload.yaml --site=cloud-stage-01
workload/api validated
$ nebctl deploy workload.yaml --site=factory-de-01
workload/api scheduled for on-site rolloutCloud convenience without on-site drift
Companies are stuck between public cloud convenience and self-managed on-prem complexity. Public cloud is easy to consume, but not every workload can live there. Self-managed edge and on-prem infrastructure gives control, but creates snowflake deployments, slow upgrades, and operational burden.
Start before hardware arrives
Create cloud-backed virtual sites for development, testing, staging, and early onboarding.
Keep the same workload path
Use Kubernetes APIs, kubectl, Helm, GitOps, and existing container workflows across virtual and physical sites.
Operate distributed sites centrally
Nebulix manages lifecycle, upgrades, observability, recovery, and fleet state from one operating hub.
Use local compute where it matters
Move workloads on-site for data locality, latency, sovereignty, regulation, or operational constraints.
Where cloud alone is not enough
Nebulix is built for organizations with many sites, local compute requirements, and central infrastructure teams that do not want every site to become its own platform.
Manufacturing fabs
Run latency-sensitive compute close to machines and production data, while central teams validate releases in cloud before rolling them out on-site.
Local AI in offices
Operate inference capacity across many offices so each site can scale locally, keep sensitive data local, and still follow one central operating model.
Warehouses and logistics sites
Deploy local compute for scanning, robotics, routing, and automation workloads without turning every warehouse into a separate infrastructure project.
A managed infrastructure platform for distributed sites
Nebulix is a control hub for workloads that need to run where the cloud alone is not enough. It is not a generic multi-cloud dashboard, not just Kubernetes on bare metal, and not only an AI appliance company.
Virtual sites give teams a managed cloud environment to validate the same workload model they will later use on physical Nebulix appliances at customer sites.
Virtual sites
Nebulix-managed cloud Kubernetes environments for development, testing, staging, and early onboarding.
Physical sites
Nebulix-owned appliances deployed at customer locations and operated under subscription.
Central operations
One control plane, API, dashboard, and CLI for virtual and physical sites.
Managed services
A curated service catalog available consistently across cloud and on-site environments.
Customers do not buy hardware. Physical Nebulix appliances are owned and operated by Nebulix, deployed at customer sites, and managed centrally as part of the subscription.
One workflow from cloud to site
Develop in cloud, validate the workload, deploy on-site, and keep operations centralized.
Start in cloud
Create a managed cloud cluster and begin development immediately.
Validate workload
Test deployment workflows, services, and operational behavior before hardware arrives.
Deploy on-site
Move the same workload to a Nebulix physical appliance when local compute is required.
Operate centrally
Manage cloud and physical sites through one dashboard, API, and nebctl workflow.
From cloud validation to local compute in a fab
A manufacturer can validate software in cloud first, then deploy the same workload to an on-site appliance when latency, production data locality, or operational constraints require compute inside the fab.
Develop in a virtual site
The platform team creates a cloud-backed virtual site for application teams to build and test against the same deployment model used later on-site.
Validate for the fab
Teams test manifests, services, observability, rollback behavior, and release gates before the physical appliance is installed.
Deploy to the physical site
When the fab needs low-latency local compute, the same workload is rolled out to a Nebulix-owned appliance at the customer site.
Operate centrally
Central infrastructure teams monitor site health, upgrades, workload state, and managed services across virtual and physical environments.
Clear responsibility boundaries
Nebulix removes site infrastructure work from application teams without taking away their deployment workflow or control over the workload.
Platform lifecycle
Cluster lifecycle, base system updates, Kubernetes upgrades, monitoring signals, and appliance health.
Maintenance windows, production release approvals, and workload compatibility testing.
Site connectivity
Control-plane connectivity, site enrollment, health reporting, and connectivity troubleshooting.
Network access, firewall approval, local power, rack placement, and site readiness.
Workload delivery
Consistent deployment targets across virtual and physical sites through dashboard, API, and nebctl.
Application code, container images, GitOps repositories, workload configuration, and rollout decisions.
Data and secrets
Infrastructure controls needed to run the platform and managed services.
Data classification, data placement requirements, application secrets, and access policies.
Managed services
Service lifecycle, upgrades, monitoring, and operational runbooks for curated infrastructure services.
Service selection, schemas, data retention needs, backup requirements, and restore approval.
Capacity planning
Physical appliance sizing guidance and subscription planning for each site.
Expected workload profile, latency requirements, redundancy needs, and growth assumptions.
Virtual sites let teams begin development, testing, and staging before appliance delivery. Physical site rollout is planned after capacity, network, redundancy, and site-readiness requirements are confirmed.
Security, connectivity, and integration points
CTOs should not have to guess how a central control plane interacts with local infrastructure. Nebulix keeps the product boundary explicit: site workloads run locally, operations are centralized, and customer systems remain part of the workflow.
Data boundary by design
Workloads and site data run where they are deployed. Nebulix does not need application data copied into a central dashboard to operate the site infrastructure.
Explicit site connectivity
Physical sites are enrolled with defined network paths, firewall rules, and health checks. Workloads continue to run locally if central connectivity is degraded.
Access and audit model
Nebulix is designed around API, dashboard, and CLI access with role separation, auditability, and customer-controlled release approvals.
Integration surface
The goal is to fit into existing platform-engineering workflows instead of forcing every site onto a separate operational island.
Kubernetes-native, operated as a product
Use familiar Kubernetes-style workflows through nebctl, while Nebulix operates the infrastructure underneath.
$ nebctl create site cloud-dev-01 --type=virtual
site/cloud-dev-01 created
$ nebctl apply -f app.yaml --site=cloud-dev-01
deployment.apps/api-service created
service/api-service created
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
api-service-7d9c8-kxm2p 1/1 Running 0 12s
api-service-7d9c8-aht7k 1/1 Running 0 12s$ nebctl validate -f app.yaml --site=factory-de-01
workload/api validated
$ nebctl apply -f app.yaml --site=factory-de-01
deployment.apps/api-service created
$ nebctl get deployments --all-sites
NAME REFERENCE SITE REPLICAS
api-service Deployment/api cloud-dev-01 2
api-service Deployment/api factory-de-01 2One workflow
Validate workloads in cloud and deploy them on-site without changing how teams work.
Nebulix-operated
Nebulix manages lifecycle, upgrades, monitoring, site connectivity, and appliance health.
Open-source foundations
Built on Kubernetes, Cluster API, Talos, and Argo CD, with Nebulix adding the product layer for cloud-to-site operations.
Curated managed service catalog
Nebulix provides managed infrastructure services consistently across cloud-backed virtual sites and on-site physical appliances. The catalog is curated, not a huge marketplace: PostgreSQL, Redis, object storage, observability, and inference runtimes are examples of the services teams can standardize around.
Estimate a physical site subscription
Use the calculator to estimate an on-site Nebulix appliance subscription. Physical appliances are ordered through sales; Nebulix owns the hardware and operates Kubernetes, monitoring, lifecycle management, and day-2 infrastructure services under subscription.
We map your capacity to Nebulix appliance nodes. Final specs are confirmed during solution design.
Estimated pricing
Nebulix-owned hardware, Kubernetes operations, monitoring, lifecycle management, and day-2 operations included
This calculator is for orientation only. Final pricing depends on location, redundancy, networking and SLA requirements.
Request early access
Start with a cloud-backed virtual site, then plan where physical Nebulix appliances should run workloads that cannot stay only in public cloud.
What you get:
- Early access to managed cloud clusters and virtual site onboarding
- Founding customer pricing
- Solution design for physical Nebulix appliances deployed at your sites
- Direct input on deployment workflows, managed services, lifecycle management, and observability