Set up self-hosted infrastructure in minutes
We automate how you set up, secure, and document self-hosted services so your team can focus on your products instead of rebuilding plumbing.
Do you keep spending time wiring infrastructure and struggling to set up internal services? Considering self-hosting to get free from BigTech lock-in? Concerned about how public LLMs handle your data? Are deployments drifting from what's documented? Have you bought another SaaS because self-hosting felt like too much hassle, or because connectivity kept breaking? Do partners require on-prem or VPC installs that make traditional SaaS irrelevant? If so, you're in the right place.
Current tools are too simple or too complex
Tools for self-hosted services fall into two camps: heavy platforms that require dedicated DevOps, or simplistic scripts that ignore networking and connectivity. Either way you still end up needing engineers to make it work.
Top-down, service-first automation
Instead of building infrastructure bottom-up, we take a top-down, service-first approach. Tell us which services you need and which machines you have, and we generate secure configs, networking, and deployment steps across your own hardware, on premises or in your VPC.
What we mean by services
By services we mean anything that runs natively or in Podman/Kubernetes: internal collaboration tools, file servers, local RAG stacks, or services hardware relies on, like DHCP or MQTT for IoT devices.
Documentation that stays current
The same source data that generates service recipes also produces documentation, so every setup is inspectable and reproducible. When you use Infraspawn, documentation stays in lockstep with what's deployed.
Ephemeral networks and infrastructure
Our connectivity layer is purpose-built to support ephemeral networks and the ephemeral infrastructure they enable. Infrastructure should be simple to set up and simple to tear down. Our mesh supports expiring networks automatically, so agents can spin up secure meshes on demand, orchestrate services across heterogeneous nodes, and clean everything up when the job is done, unlocking truly agentic, on-demand infrastructure.
Current focus: PropTech challenges
Infraspawn is in active development and available today via our pilot. We're partnering with industrial and PropTech teams to deliver the services their sensors, IoT devices, and HVAC systems need: DHCP, MQTT, Fieldbus, BACnet, and more. This domain constantly wrestles with deployment, connectivity, and documentation challenges, a perfect fit for Infraspawn.
1. Design your setup
Create networks, choose the services you need, and map them to the right nodes.
2. Install the agent
Install a lightweight daemon on each node you want managed; it adds a secure interface for every network you set up.
3. Automate
Each agent fetches service recipes, applies the right policies, and orchestrates deployment for you.
A very simple example using Infraspawn to host a wiki on an internal network.
FAQ
What can I deploy with Infraspawn?
Wherever you need to self-host services and need secure connectivity to them, Infraspawn will likely be a good fit. For now we focus on backend services needed by IoT devices used in factories and PropTech.
How fast can I be up and running?
If the services you need are supported, minutes. Install the agent on your nodes and let automation take over.
What if a service isn't supported yet?
Tell us what you need and we'll prioritize it. You can also run custom images with today's primitives if you already have a container build. This works by first assigning a 'container registry service' to a node, then upload your image to the registry once it's available. Then assign the 'custom image service' to the nodes you want to host your service on, and point it to the image you uploaded. We are looking into mechanisms to make this process simpler.
Do I need Docker/Podman or Kubernetes expertise?
No. We handle networking, policies, image and container creation, and deployments for you. After service assignment, you can fetch the container setup generated, as if you had the expertise hired, the task was done and documented.
How is connectivity handled?
Infraspawn ships with a custom zero-trust mesh that secures traffic between nodes and handles NAT traversal automatically - no manual VPN wrangling. In cases where NAT traversal is needed, but fails, we fallback to relaying and warns the admin user accordingly.
This is too much black box magic for my taste.
We generate documentation from the same source data we use to create service recipes, so you can see exactly what's deployed and how it's configured.
I want to sign up. When will this be self-service?
Once we've rounded out the right portfolio of supported services, we'll roll it out as a full self-service product. Help us achieve this faster by signing up for a pilot and become a collaborator.
Supporters & Partners
