A Sri Lanka-based engineering practice. The direction is set by the person who writes the framework underneath it, and it stays set through the build.
Founder & principal architect
Author of Vortos, the event-driven PHP framework this practice builds on. It is public, installable and readable before you talk to us. Sets the architectural direction on every engagement: Domain-Driven Design, event-driven systems, and the boundaries between them.
Systems & release
Works on deployment, monitoring and release across our systems.
Infrastructure
Works on cloud environments, containers and the delivery pipeline.
Product engineering
Works where the API contract meets the interface, on web and mobile.
Backend engineering
Works on domain logic and the data access underneath it.
The architecture has one author, and that is who you talk to. Direction is set by the person who then writes the framework it runs on, not by an account layer relaying it.
We don’t sell an engagement with one team and staff it with another. The people on the first call are the people on the last commit.
Decisions, trade-offs and the reasoning behind them get documented as they are made. When we hand a system over, the thinking comes with it.
Start a project
Send the shape of the problem. A paragraph is plenty. You get back how we’d build it, what it would take, and what the first two weeks look like. It comes the same day, from the engineers who would do the work.