Engineering
What you can hold us to.
The standards every engagement is delivered against, and the stack we reach for by default. If a proposal from us does not match this page, ask us why.
Principles
How we work
Security is scoped, not assumed
We are the engineering division of a cybersecurity company. A threat model is part of discovery, dependency and secret scanning run in the pipeline, and security work appears as a line in the proposal with a price next to it.
Done means running in production
A system is finished when it handles its failure paths, emits the telemetry needed to debug it at 2am, and ships with a runbook. A demo that works on the happy path is not finished.
Launch is a milestone, not an exit
Most of a system's life happens after the first release. We stay on to operate it, watch what production teaches us, and ship the next release. The engagement is sized to the life of the system, not to the launch date.
Scope you can hold us to
The proposal names what we will build, what we won't, and what it costs. If the timeline is unrealistic we say so before we start, not in month three. Changes to scope are written down and re-priced.
Boring technology, chosen for your team
TypeScript for applications, Go for services that have to be fast, Python for data, Rust when it matters. We pick what you can hire for, so the system is never hostage to one vendor, including us. A stack only we can staff is the wrong stack.
You own it, whoever runs it
Code, infrastructure, and documentation live in your repos and your cloud accounts from the first commit. If you ever want to take the work in-house, the handover is a checklist, not a project. We build that capability in from day one, whether or not you ever use it.
Stack
What we reach for by default
If your estate already runs on something else, we work in that. The stack has to be one you can hire for, so the system never depends on us, even while we are the ones evolving it.
languages
frontend
backend
data
infra
cloud
Family
Who you are hiring
Corporate IO is the engineering division of S-Tech Solutions, a Johannesburg cybersecurity company. The same people who test systems under adversarial pressure review what we build, which is why security is a priced line in our proposals rather than a promise.
Our open-source tools and technical writing live at S-Tech Labs. If you want to check the quality of our work before talking to us, start there.
- S-Tech Solutions
Cybersecurity & Defense
Corporate IO
Software Engineering
- S-Tech Labs
Open Source & Research
Hold us to this page.
Send the problem. The proposal you get back is written to these standards: what done means, what it costs, what we will not build, and what happens after launch.