An independent systems practice
We help small engineering teams troubleshoot deployments, simplify infrastructure, and verify recovery. Each engagement has a defined scope, recorded checks, and operating notes your team can use.
A focused investigation
We investigate what is happening, what the evidence supports, and what it would take to resolve it. You receive findings and a recommended next step, including uncertainties that need more work.
Scope and fees are agreed before paid investigation begins. Implementation is agreed separately; an investigation does not guarantee a fix.
Discuss an investigationWays to work together
Prepare for a launch or migration, simplify an existing system, or plan its ongoing maintenance. Each service starts with an agreed scope and completion checks.
Prepare for change. Test the way back.
Review deployment, access, backups, and recovery before a launch, migration, or major upgrade. Identify gaps and implement the fixes that matter to your team.
Make the system easier to run.
Review the dependencies and manual work behind your applications. Remove unnecessary components and consolidate overlapping tools around the systems you need to keep running.
Keep necessary changes moving.
Plan and apply dependency updates, platform upgrades, and configuration changes through a regular schedule, with checks and recovery steps appropriate to each change.
These are planned engagements. Support hours and response arrangements are agreed explicitly; ongoing emergency coverage is not included by default.
How the work happens
We work from the system you have and the constraints around changing it. The work should leave your team able to understand and operate the result.
Establish the problem, dependencies, access requirements, and constraints before choosing an approach.
Set out the deliverables, responsibilities, and completion checks in a written proposal.
Make reviewable changes in your repositories and accounts where practical. Test the agreed behavior and recovery steps.
Walk through the result, document remaining limitations, and agree on any ongoing work separately.
Selected open-source work
These projects show how we approach infrastructure and developer tooling. Explore their source, installation instructions, and documented limits.
Infrastructure automation
Manage Cloudflare Tunnel, DNS, and Access through Kubernetes resources. The project documents resource ownership, recovery after interrupted operations, and controlled configuration changes.
Alpha software. Review the release and operating limits before deployment.
Developer tooling
Build and maintain Minecraft modpacks from the command line. empack handles dependencies, resumes restricted-download workflows, and preserves project configuration during cleanup.
A Minecraft modpack tool with documented workflows and failure handling.
Open-source work by inherent.design. Source, requirements, and operating limits are documented with each project.
Before we start
No. We start with your operating needs. A simpler outcome may involve managed services, fewer tools, or removing Kubernetes where its costs outweigh its benefits. We confirm technical fit before agreeing to work.
Yes. The first step is understanding what you run and who depends on it. Replacement is an option to evaluate, not an assumption. Access, change windows, and responsibilities are agreed before implementation.
An initial conversation establishes the problem and whether there is a useful engagement. We then propose a scope, deliverables, and fees. Any discovery work that needs to be paid is agreed before it begins.
Start a conversation
Tell us what you run, what is difficult today, what a useful result would look like, and any deadline or constraint. We will first establish whether the work fits and what needs closer inspection.
hello@inherent.designPlease leave credentials and confidential system details out of the initial message.