We own the outcome, not a seat on your team.
A client can bring a whole product or one engineering area inside a product somebody else is building. Either way the responsibility is an engineering result, and the people who scope it are the people who write it.
Engagements
What we build and run.
Red Sentra builds software to a requirement rather than assembling it from a template. The same engineers scope the work, write it and stay with it once it is live.
Red Sentra takes over running applications and keeps them running: incidents, production defects, upgrades, deployment and the ongoing engineering a live system needs.
Red Sentra builds web applications as systems: the architecture, the services behind the interface, the data, the deployment and what happens once real traffic arrives.
Red Sentra builds mobile applications together with the services behind them, ships them to a store, and keeps operating them once real devices are involved.
Red Sentra designs and builds APIs, and connects systems to the ones that already exist — including the protocols that are hostile, stateful or badly documented.
Red Sentra takes responsibility for the infrastructure and the delivery path a system runs through — how it is shaped, how a change reaches production, and what happens when it should not have.
Red Sentra builds AI capabilities into software that has to keep working: the inference path, the services around it, and the rules that decide when the feature is allowed to speak at all.
Also engaged
Work we take that has no page of its own.
These are sold and real. They do not have a page here because a page exists to answer a question somebody typed, and for these the question arrives in a conversation instead.
Infrastructure, DevOps and delivery
Designing and running the infrastructure a system lives on, the deployment path, and the observability that makes the next failure legible. Taken as a responsibility, not supplied as an engineer under somebody else’s management.
Architecture and technical consulting
Reviewing an architecture, scoping a rebuild, or answering one hard technical question with an engineer rather than a deck. A focused engagement with a defined end, not a retainer.
Backend and distributed systems
The largest part of what the team does, present in every engagement above rather than sold separately. Six of the published systems declare a backend contribution.
AI features inside a product
An assistant, a model behind an interface, or a retrieval layer — always with an explicit boundary on what it may claim. Built into a product, not sold as a category of its own.
Boundary
What we do not sell.
Red Sentra does not supply engineers as embedded headcount. “Give us three developers to work from our backlog” is not an engagement we take, and neither is a named engineer reporting to somebody else’s manager for six months.
Fixed price, monthly, milestone or time and materials are all possible. The billing shape is not what makes the difference — owning the result is.