Cloud platforms and software built for production.

• P—01

  Senior from day one

  The engineer who scopes your project is the one who builds it. Nothing is handed down to a junior team.

• P—02

  In writing, on your time

  Proposals, updates and decisions are written down. A call happens only when it helps — never as a sales step.

• P—03

  Fixed scope first

  We start with a defined deliverable and a fixed price, so you can judge the work before committing to more.

• P—04

  Your accounts, your code

  Everything lives in your repositories and cloud accounts, documented from the first commit. No lock-in.

• P—05

  Pragmatic technology

  We choose the simplest tool your team can run. Every significant choice comes with its trade-offs in writing, including the options we rejected.

• P—06

  Confidential by default

  We never name clients, show their systems or reuse their data. What we see in your environment stays between us, under your NDA if you have one.

1. 01

   Discovery & Assessment

   Read the system before changing it: architecture, costs, risks, delivery and the goal behind the request.

2. 02

   Architecture & Planning

   Options with their trade-offs, a chosen design and a sequenced plan — written down before work starts.

3. 03

   Implementation

   Small, reviewed changes in your repositories and accounts, as code, in short cycles.

4. 04

   Validation & Reliability

   Load, failure and restore tests, SLOs and alerts: evidence that the system behaves as designed.

5. 05

   Knowledge Transfer

   Runbooks and documentation so your team owns the result, then improvement driven by measurements.

1. N—01

   Error budgets and burn-rate alerts: paging for the right reasons

   How to turn an SLO into alerts that fire fast on real outages, stay quiet on noise and stop paging once the problem is fixed.

   →
2. N—02

   A production baseline for Kubernetes workloads

   Requests, probes, disruption budgets, graceful shutdown and pod security: the settings a production Deployment should have before its first incident.

   →
3. N—03

   Terraform in a team: state layout, blast radius and reviewed plans

   How to split Terraform state, run plans in CI and apply only what was reviewed, so infrastructure changes become routine instead of risky.

   →
4. N—04

   Build once, promote by digest: a delivery pipeline you can roll back

   A reference delivery path where the artifact tested in staging is exactly the one in production, and a rollback is a redeploy of the previous digest.

   →

Products we designed, built and still operate ourselves, on the same stack we bring to client work. They are our public proof: every one is live — open any.

Mobile apps

SeuÔnibus

Buses on the map, arrival times at your stop and which line to take, in some of Brazil's largest cities.

Coming soon to Google Play

Games