Calera is a small, senior studio for the part of the company nobody puts on the marketing site — the queues, the handoffs, the spreadsheets-that-shouldn't-be-spreadsheets. We design and ship the infrastructure that quietly does the work, so the people you hired for judgement get to spend their week on judgement.
CALERA RUNTIME
OPS=PIPELINE-V3
UTC 2026-06-24
-
calera —status —verbose
system:
operational
pipeline:
47 active
/
3 queued
uptime:
99.8%
(32d 14h 07m)
-
calera watch —pipeline invoice_processing
:invoice_processing
LIVE
:crm_sync
done
/
+12%
:vendor_recon
reconciling
3 DELTA
:alert_handler
watching
IDLE
-
calera log —tail 1
[07:41:01] invoice processing - batch_099 completed : 214 records . 0 errors
|
ENV PRODUCTION
REGION
AP-SOUTHEAST-1
PID
2847
The non-negotiables that keep our systems boring, durable, and uncomfortably effective.
We don't sell hours. We deliver durable systems that keep producing leverage long after we're gone.
Every engagement starts with the operational map — where work enters, where it stalls, and where it leaks value.
We choose tools the team already pays for. Novelty is a liability when uptime matters.
Automation handles repetition. Judgement, escalations, and exceptions stay with the people they belong to.
Aggregate numbers from the last twelve months — measured at the workflow level, with telemetry, on real production traffic. The interesting metric is rarely the percentage. It's what the team finally has time to do instead.
Every engagement is led by a senior operator and a senior engineer. No account managers, no hand-offs, no juniors learning on your time.
Alex Marín
Studio lead · Systems architect
Twelve years building back-office infrastructure for fintech and logistics. Reads the org chart before the requirements doc.
2022
Studio founded in Lisbon
Two operators and a manifesto: stop selling dashboards, start shipping systems.
2023
First fintech engagement live
Document intake and KYC routing for a regulated lender. 4× throughput on affected workflows in 60 days.
2024
Agent layer added to every build
Reasoning + tool-use becomes default architecture. Validators and fallbacks become non-negotiable.
2025
24 systems running in production
Across logistics, finance, healthtech, and ops-heavy SaaS. 99.8% aggregate uptime, zero handover regressions.
2026
Q1 — two engagements open
Selective by design. We take the work we can ship to the bar above, then we close the queue.
A short trajectory, on purpose. We grow by the systems we keep running, not the logos we collect. Every quarter is judged by what stayed live, not what shipped.
Why does the same lead get touched four times before reply?
Why does every new client cost half a week of ops?
Why does the same Slack question come up every Tuesday?
