Network & Backend Engineer · Rust DNS Infrastructure · OpenWrt / RouterOS Tooling
Programmable DNS · Practical routing · Infrastructure that operators can trust
OxiDNS Ecosystem · Engineering Focus · Profile Snapshot · Connect
I build infrastructure tools for people who care about network control, operational clarity, and systems that can be debugged under pressure.
At the moment, my public work is centered on OxiDNS: a programmable DNS engine and its surrounding router-side tooling. I want the profile to make one thing obvious: I am interested in practical infrastructure, not toy demos.
What I bring:
- Deep interest in DNS, routing behavior, and network operations.
- Backend engineering experience for reliable APIs and maintainable services.
- A product-minded approach to operator experience: configuration, logs, deployment, and recovery matter.
- Willingness to cross layers when needed: Rust core, Java backend, shell automation, RouterOS / OpenWrt integration, and UI glue.
Thesis DNS can be a practical control plane for network behavior
Main users Router / homelab / infrastructure operators who need transparent control
Current focus OxiDNS engine, OpenWrt management, RouterOS routing workflows, repeatable builds
Design taste Fast, explicit, debuggable, configuration-driven, and operator-friendly
Not isolated repos — a connected toolkit that goes from DNS decision-making to router deployment.
|
A high-performance, programmable DNS engine in Rust with flexible pipeline-based routing. Role: the core engine for DNS policy orchestration, network-aware routing, and production-oriented performance.
|
LuCI management app for running and managing OxiDNS on OpenWrt. Role: makes OxiDNS easier to deploy, configure, and operate from router-oriented environments.
|
|
A practical traffic bypass and policy-routing solution based on OxiDNS and RouterOS. Role: turns DNS decisions into a deployable network routing workflow for real RouterOS environments.
|
A build template for packaging and distributing OxiDNS more consistently. Role: supports repeatable builds and lowers the friction for releasing or adapting OxiDNS deployments. |
I intentionally keep the front page focused:
- Showcase: active infrastructure projects around DNS, OpenWrt, and RouterOS.
- Support: build templates and integration helpers that make the ecosystem easier to ship.
- Hidden from the spotlight: forks, archived repositories, experiments, and one-off utilities that do not represent my current technical direction.
Network Systems DNS engines, policy routing, RouterOS / OpenWrt integration
Backend Engineering Java / Spring Boot, API design, service reliability
Performance Rust, efficient implementation, production-oriented tuning
Troubleshooting Logs, stack traces, packet / routing behavior, root-cause analysis
Product Thinking Operator experience, configuration clarity, maintainable workflows
Good infrastructure software should be:
- Explicit: behavior should be visible from configuration and logs.
- Composable: small pieces should connect into real deployment workflows.
- Operational: easy to run, upgrade, debug, and recover.
- Fast where it matters: performance should support reliability, not just benchmarks.
Identity Network / backend engineer building operator-facing infrastructure
Primary theme DNS infrastructure and practical network control
Main project OxiDNS ecosystem
Languages Rust, Java, JavaScript, Shell
Platforms Linux, OpenWrt, RouterOS
Best fit Network tooling, backend services, router-side integrations
Good reasons to reach out:
- You are building or using DNS / router-side networking tools.
- You care about practical infrastructure, not just benchmark demos.
- You want to discuss OxiDNS, OpenWrt / RouterOS integration, or backend reliability.
📫 Email: isvenshi@gmail.com · 🐙 GitHub: github.com/svenshi
Designed around clarity, control, and operational trust.