Bismarck, North Dakota
Software that runs when nobody is watching.
I'm Ryan Brinkman. I build systems that operate unattended and keep an honest record of what they did, and I run them myself before I offer that work to anyone else. I take on freelance and contract work in automation, data infrastructure, and applications that have to keep running.
- Running unattended since
- 31 May 2026 Nexus on Railway, measured 24 Sep 2026
- Automated tests passing
- 5,488 Nexus suite, measured 24 Sep 2026 on the commit in production
- Longest-running system
- 116 days Nexus in daily use, measured 24 Sep 2026
Work
What I have built and what it is doing now. The status beside each one is what is true today, not what is planned.
-
E-commerce prototype
past client engagementA storefront prototype developed for a retail client engagement. The work is currently sidelined and is not a live production service.
-
Nexus
nexus.brinkmandynamics.comA guided, paper-only trading workflow system: market data, planning and review in one place, with every figure carrying where it came from and how old it is. Running unattended on Railway since May 2026.
-
Nexus OmniSense
Authorized network inventory and visibility for systems I own and operate. A Raspberry Pi appliance and Android client provide one console for topology, asset status and connection health in one operational view.
-
Android network visibility client
A Kotlin and Jetpack Compose operator app for viewing authorized network inventory, node status and diagnostic summaries from systems I own and operate. Its focus is dependable field access and clear operational state.
-
Cortex
Orchestration for the engineering agents that build and maintain the systems above, with every task, decision and result kept on record and auditable after the fact.
How I work
Unattended software fails differently from software someone is watching. These are the rules that make the difference.
Measured, not asserted
A number on this site was taken from the running system on a stated date. If it was not measured, it is not written down.
Refuse rather than guess
When a system is not sure enough to act, it declines and records why. A wrong action costs more than a skipped one.
Instruments that cannot lie
A dashboard that reports success while doing nothing is worse than no dashboard. Every status has to be falsifiable.
Nothing irreversible by accident
A person decides anything that cannot be undone. Nexus has run paper-only since its first deploy, and that is a design rule rather than a setting.
Work with me
Available for freelance and contract work: automation, data infrastructure, and applications that have to keep running when nobody is looking. Tell me what the system has to do and what it must never do.
contact@brinkmandynamics.com