A web application is a system with a browser attached.
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.
Responsibility
What we take on.
- Product and system architecture, including the boundary between client and server
- The backend the browser talks to, and the contract between them
- Authentication, authorisation and the data model underneath
- Deployment and the release path
- Operation of the running application
Engineering
The interesting part is behind the interface
Most of the decisions that determine whether a web application survives contact with real use are not visible in the browser: where state lives, what is allowed to fail, how a write and the event describing it stay in agreement, and what happens to a request that arrives twice.
Lexora is the clearest example in the portfolio. Its Rust backend commits a state change and its events in one transaction through an outbox, and background workers do the slow work outside the request path.
Where the boundary is drawn
A client and a server disagreeing about who owns a piece of state is the source of an entire class of bug that looks like a rendering problem and is not. The boundary gets decided deliberately, early, and written down as a contract rather than discovered later.
That contract is usually an API, and the same rules apply to it as to any other interface Red Sentra builds: one shape, versioned, and honest about what it does not do.
Running it afterwards
A web application is not finished at launch: dependencies move, platforms deprecate, and the traffic pattern is never the one anybody predicted. Deployment, observability and upgrades are part of the engagement rather than a separate purchase.
Where a client wants only the ongoing part, that is the maintenance and support engagement instead.
Evidence
Systems this rests on.
Each entry names the contribution Red Sentra declared on that system. Nothing here is cited for work the content model does not carry.
Lexora
A Rust backend with an event-driven core running on Cloud Run, built and operated for a commissioned product that is live today.
Lexora
The transactional outbox: a state change and its events committed together, so publication can fail and be retried without the data telling a story that is not true.
Limits
What this page does not claim.
- Red Sentra’s declared contribution to Lexora is architecture, backend, reliability and operations. A web front end is not among them, and this page does not claim one.
- No portfolio of web applications is claimed. One commissioned product with a published backend is the evidence, and it is stated as exactly that.