Roadmap
Conn3x closes the gap between creating infrastructure and configuring it: one plan, one state and one apply for the cloud and the servers in it. Today it does that for Linux. Windows is next.
This page says what’s planned and in what order. None of it has a date, and nothing here works until a release says it does. The release notes are the record of what has shipped.
- Linux hosts. Conn3x configures Rocky Linux, RHEL, AlmaLinux, Fedora, Debian and Ubuntu. Every change to Conn3x is tested on Rocky Linux 10, Fedora 45, Ubuntu 24.04 and Debian 13.
- 100 official circuits. Web servers, databases, monitoring, Kubernetes, DNS, VPNs, hardening, identity, detection and response, vulnerability scanning, compliance tracking, CI runners and a private AI stack, each pinned to a release and tested on the distributions its page lists. The circuit catalogue has them all.
- The Circuit Builder. Pick a distribution and the circuits you want, fill in a short form, and get a config that’s ready to plan. k3s, Zabbix, FreeIPA and Velociraptor take their hosts by role, servers on some and agents or clients on others. It can also create the servers on DigitalOcean, Google Cloud, AWS or Azure, in the same plan. Azure here means Linux hosts, with Windows still to come. It won’t let you pick two circuits that fight over a port, and CI validates every circuit it offers, alone and in a set of realistic builds. Your picks live in the page address, so you can share a build as a link.
- AI you can account for. A private AI stack from circuits: Open WebUI and Ollama for chat that stays on your servers, a LiteLLM gateway with per-team keys and budgets, Presidio masking personal data before a model sees it, and Langfuse keeping a trace of every call.
- Your playbooks come with you.
conn3x convert ansiblerewrites the tasks it can prove and marks the rest with the reason. - Any OpenTofu provider. Conn3x runs the same providers OpenTofu does, so it creates resources on AWS, Google Cloud, Azure, DigitalOcean and the rest. Examples tested end to end exist for DigitalOcean and Google Cloud, including BigQuery.
- Runs on Linux and macOS, on amd64 and arm64.
Now: Windows
Section titled “Now: Windows”Windows servers, configured from the same plan as the cloud they run in. As with Linux hosts today, the plan shows every change before it’s made, and conn3x drift checks Windows hosts as well as the cloud resources around them. None of this works yet.
Azure comes with this work. The Circuit Builder already creates Azure VMs for Linux hosts, tested on real ones, but not for Windows. The Windows work adds tested examples that create Windows VMs on Azure and configure them in one apply, as circuit-caddy does on Google Cloud.
The test we’re aiming at is a whole Active Directory lab, domain controllers and member servers, built and configured from one config.
Next: another round of circuits
Section titled “Next: another round of circuits”New circuits pause while Windows gets built. Requests still count: the last batch came from lists people sent us, so keep them coming and they’ll go into this round.
After that: network devices
Section titled “After that: network devices”Switches, routers and firewalls, configured over their own management interfaces, in the same plan as the hosts behind them.
macOS hosts.
The Circuit Builder as an app: desktop apps for Windows and macOS, and phone apps for iOS and Android.
Help shape it
Section titled “Help shape it”Open work is in GitHub issues, and every circuit repository has good first issues if you’d like somewhere to start. The order on this page moves when people tell us what they need. If Windows, network devices or a circuit you’re missing matter to you, say so in Discussions. See Get involved for other ways to help.