DNS
Authoritative DNS services, zone management, health-aware responses, and future global routing support.
UpLion is building an open edge infrastructure platform: authoritative DNS, smart reverse proxying, TLS termination, config-driven routing, and a control plane designed for globally distributed edge infrastructure.
Anycast/BGP foundation exists. We are building the core engineering team for the control plane, edge config management, and platform layer.
UpLion is being designed around a simple idea: edge infrastructure should be programmable, observable, and open from the beginning.
The platform starts with DNS, reverse proxying, route configuration, and traffic forwarding. From there, it can grow into health-aware routing, TLS automation, metrics, rules, caching, WAF-style protections, private edge deployments, and eventually Anycast-based global points of presence.
This is systems work: Go services, routing logic, Linux networking, config distribution, observability, and careful operational design.
Six surfaces, one coherent platform. Each layer is independent enough to evolve, and integrated enough to feel like one product.
Authoritative DNS services, zone management, health-aware responses, and future global routing support.
A programmable reverse proxy layer for host/path routing, TLS termination, backend forwarding, and traffic control.
Central configuration, route management, service metadata, health checks, deployment state, and API-driven control.
Built with pragmatic open-source foundations and designed to integrate with tools like HAProxy, Apache Traffic Server, Terraform, Consul, Nomad, Vault, and other infrastructure systems.
A path toward distributed nodes, regional routing, observability, and eventually Anycast/BGP-based edge presence.
A clean dashboard, API, CLI, docs, and workflows for managing traffic infrastructure without hiding the underlying mechanics.
UpLion is not a polished product yet, but it is not starting from zero. We already have working Anycast/BGP infrastructure, a clear edge architecture, Salt-based deployment, and early edge/proxy components.
The next stage is turning that foundation into a coherent platform: a control plane, dashboard, APIs, edge configuration management, and automated workflows for HAProxy, Apache Traffic Server, routing, certificates, and deployment state. Some configuration is still hard-coded today — the important work now is making the edge programmable, observable, and manageable through a proper control plane.
We are looking for founding engineers who want ownership from the architecture and platform-shaping stage, not just implementation tickets.
Roadmap snapshot
We are forming the first core engineering team around UpLion's next stage: turning working edge/network infrastructure into a programmable platform. These are high-ownership roles for people who like infrastructure, distributed systems, open-source software, and practical systems engineering. The product layer can move quickly with Bun and TypeScript, while the core control plane and edge runtime are built in Go.
Washington, DC / Maryland / Northern Virginia preferred. We are building the founding team with a local-first rhythm — ideally meeting in person once a week or a few times per month. Remote candidates may be considered for exceptional infrastructure or open-source experience.
Core Go services, edge proxy, config distribution, and platform APIs.
What you'll work on
Good fit if
You have strong Go experience, understand networking fundamentals, and enjoy building systems where reliability, latency, and operational clarity matter.
HashiCorp ecosystem, HAProxy, ATS, Linux networking, automation, and OSS integration.
What you'll work on
Good fit if
You are comfortable reading source code, scripting, debugging Linux systems, and deciding when to build versus integrate.
Public website, dashboard, Bun backend-for-frontend, and developer experience.
What you'll work on
Good fit if
You care about polished interfaces, developer tools, TypeScript/Bun workflows, and making infrastructure understandable without making it simplistic.
UpLion is early. That means the architecture, engineering culture, and product direction are still being shaped. If you want to work on DNS, routing, proxying, control planes, global infrastructure, and open systems, we would like to talk.
Send a short note, links to relevant work, and which founding role fits you best.