Frequently asked questions
Short answers about what we do and how we work. If your question is not here, ask us directly.
What kind of work do you do?
Software engineering for server-side systems: API gateways and traffic management, event-driven backends, application security and tokenisation, resilience and high availability, and the modernisation of legacy services and data pipelines.
Do you build new systems or improve existing ones?
Both. Many engagements start with an existing platform that has a specific problem – latency, outages, security findings or a migration deadline – but we also design and build new components.
How do you approach an API integration?
We start from the contract: an OpenAPI or AsyncAPI description, error semantics, idempotency rules and versioning. Then we agree on authentication, rate limits and observability before writing integration code, and test against recorded and synthetic traffic.
How do you make a system scale?
By finding the actual constraint first. We measure tail latency and saturation per route, then address the bottleneck – caching, connection management, horizontal scaling, queueing or data-model changes – and verify the result with load tests against agreed budgets.
How do you approach resilience?
We define service-level objectives with you, analyse how critical paths fail, design topologies that tolerate the failures that matter, and rehearse recovery. A resilience engagement ends with tested runbooks, not just a design.
How do you handle security?
Security is part of design, not a final check: threat modelling, least-privilege access, mTLS between services, secrets in a vault, sensitive fields tokenised, and automated checks in the delivery pipeline.
Which technologies do you use?
We choose per problem and prefer well-understood tools: Go, Node.js, PHP and Python for services; Kafka or NATS for events; PostgreSQL; Envoy, Kong or NGINX at the edge; Kubernetes, Docker and Terraform for infrastructure; OpenTelemetry and Prometheus for observability.
Can you modernise a legacy PHP or monolithic application?
Yes. We prefer incremental strangler-fig migrations: characterise current behaviour with tests, route traffic through a facade, extract one capability at a time and retire old code only when the new path is proven.
Do you work with regulated companies?
Yes, as an engineering provider. We implement technical controls for requirements that your legal and compliance teams define. We do not provide financial, payment or banking services or legal advice.
How do we start?
Send the booking form with a short description and two possible times. We reply by email, hold a scoping session and, if there is a fit, send a written proposal. The request itself is non-binding.
Have a system that needs to scale or be secured?
Tell us about the architecture, the bottleneck or the deadline. We reply by email to agree a time for a scoping session.