Connect the estate.
Bring remote servers and managed nodes into one topology through outbound, mutually authenticated connections.
Operate the systems
you own.
Keep them yours.
We build Gateway — an AI-first, self-hosted infrastructure control plane that makes operational change explicit, reviewable, and fully usable without AI.
01 / Flagship product
Gateway
A self-hosted infrastructure control plane for the systems you own.
Gateway brings servers, services, containers, networks, domains, certificates, and data into one operational surface — so teams can understand current state, make scoped changes, and retain control.
View Gateway on GitHubOperate the stack.
Work across services, containers, domains, certificates, files, databases, delivery, and the dependencies between them.
Control every change.
Keep permissions, approval, execution progress, audit history, and post-change verification attached to the operation.
02 / Product principles
Automation should make decisions more legible — not less.
Gateway is built around an operating model that keeps ownership visible even as the system becomes more capable.
Intent before commands.
Gateway starts from the result the system needs — not a guessed shell command. The proposed path stays readable before any work begins.
Context stays visible.
Plans are grounded in live resources, dependencies, and current state. Assumptions and missing information are surfaced instead of being buried inside automation.
Permission before action.
Human operators, integrations, and AI share explicit access rules. Approval is tied to named resources and a visible scope — not a blanket promise that the automation will behave.
Verification closes the loop.
A successful command is not the same as a successful outcome. Gateway checks the resulting state and keeps the evidence attached to the operation.
Manual paths stay complete.
AI Workspace can shorten the route, but every infrastructure surface remains available through the console and APIs. Guidance never becomes dependency.
Ownership stays with the operator.
The control plane is self-hosted and managed nodes connect outbound. Infrastructure, credentials, and the operating model remain under your authority.
03 / Also by Wiolett
Agent Marketplace
One installable source for durable memory, explicit workflow state, and disciplined review across Codex and Claude Code.
The tooling behind how we build
Context that survives. Work that stays inspectable.
Install a coherent engineering system instead of assembling isolated prompts, hooks, and review conventions by hand.
View on GitHub04 / Engineering
Selected engineering work, closer to the product.
We still take on focused infrastructure work where our product depth can materially improve deployment, integration, or long-term operation.
Deploy
Gateway installation, node rollout, infrastructure migration, and operational handover.
Integrate
Identity, delivery, cloud, data, and internal workflows connected to the operating model.
Harden
Access boundaries, observability, recovery paths, and day-two operational reliability.
05 / Contact
Talk to the people building Gateway.
Evaluating the product, planning a deployment, or working through a difficult infrastructure boundary? Start with the system and the constraint.
Telegram · @WiolettIndustries