Software engineering studio · Madrid
We design and build distributed systems, high-concurrency backends and mobile apps for teams that can't afford to go down — and we run our own SaaS products on the same foundations.
Targets we design for
01 / Capabilities
One team for the whole path: backend, infrastructure and the apps your users hold in their hands.
Event-driven architectures, replication and multi-region deployments designed to degrade gracefully instead of falling over. We treat partial failure as a design input, not an incident.
replica
leader
replica
Go and Rust services built for sustained load: WebSockets, streaming, queues and back-pressure done right.
iOS and Android apps with offline-first sync, real-time updates and release pipelines you can trust.
We build and operate our own SaaS on the same stack we deliver to clients — multi-tenant, metered and observable from day one.
Infrastructure as code, CI/CD and observability on GCP, AWS and Kubernetes, so every deploy is boring.
02 / Engineering
Most outages are designed in long before they happen. These are the rules we build by.
Metrics, traces and structured logs ship with the first commit. If we can't see it, we don't call it done.
Timeouts, retries, idempotency and circuit breakers are decided up front, then tested with real load.
Proven databases and protocols at the core; new technology only where it earns its place.
Trunk-based development, preview environments and automated rollbacks keep change cheap and safe.
03 / Stack
No framework loyalty. We pick what fits the load profile, the team that will own it and the budget.
04 / Process
Small senior team, short feedback loops and no surprises on scope or cost.
01 · 1–2 weeks
We map the domain, the load profile and the constraints. You get a written technical brief and an honest estimate.
02 · 1–3 weeks
Architecture, data model and failure modes on paper, with load tests planned before the first line of production code.
03 · iterative
Two-week increments, deployed to real environments. You see working software, not status reports.
04 · ongoing
Monitoring, on-call and continuous improvement — or a clean handover to your team, with runbooks and docs.
Tell us what you're building. We reply within one business day with questions, not a sales pitch.