[ Vol. 04 / Field Doc ]
Queto
↓ 1.1 / Introduction
ABOUT
Queto is the runtime for teams who refuse to assemble their stack from twelve vendors, three dashboards and a stack of YAML. We collapse compute, data and observability into one programmable surface — so a four-person team ships like a four-hundred-person team. We were founded in 2023 by infrastructure engineers from Stripe, Vercel and Datadog.
1
1.2
OUR STUDIO
we don't build features. we build the floor every other tool stands on — the quiet substrate that lets ambitious software exist at all.
↓ (Capabilities)
- Edge Compute
- Data Primitives
- Observability
- Workflow Engine
- Identity & Auth
- Vector & Search
- Event Streaming
- Secrets & Vault
- Cron & Schedulers
- Feature Flags
- AI Inference
- Audit & Compliance
↓ (Recognition)
- 5× InfoQ Top Tools
- 4× GitHub Trending
- 3× ProductHunt #1
- 3× Y Combinator W23
- 2× Fast Company Innovation
- 2× Forbes Cloud 100
- 2× a16z Open Source 50
- 1× ACM SIGOPS Mention
- 1× CNCF Sandbox Project
- 1× Wired Top 25
↓ (Image description / credit)
OPPORTUNITY
↓ Stage
↓ Name
↓ Insight
1
GAP
Modern teams stitch 9–14 vendors to ship one product. The cost is hidden — not in license fees, but in on-call rotations, vendor migrations and the engineers who quit after them.
2
SHIFT
AI workloads broke the assumption that compute is cheap and predictable. Teams need a runtime that treats latency, GPU cost and data gravity as first-class primitives, not afterthoughts.
3
WEDGE
Queto enters at the platform team — the four engineers everyone else complains about — and earns the rest of the stack by removing pages, not selling features.
PROCESS
↓ Stage
↓ Name
↓ Includes
1
DISCOVER
We profile your stack — workloads, latency budgets, data gravity, runtime cost — and benchmark every primitive against your real production traffic, not a synthetic demo.
2
DIRECTION
We deliver a migration architecture: what moves first, what gets replaced, what stays. Risk is mapped per service, not per quarter.
3
DESIGN
Workload graph, data shape, control plane and operator handbook are co-designed with your team in two-week shipping cycles.
4
DELIVERY
Cutover happens behind feature flags with live shadowing. We don't leave until your P95 is healthier than the day before we arrived.
PROOF
↓ Stage
↓ Name
↓ Includes
1
IMAGINE
- + Runtimes that fit how your team already thinks.
- + Infra that exposes intent, not implementation.
- + Tools that evolve as fast as your product does.
2
BUILD
- + Modular primitives that compose, not collide.
- + Operators empowered to ship without escalation.
- + Code paths that stay legible at production scale.
3
MEASURE
- + Performance proven by user-perceived latency.
- + Reliability proven by uneventful weekends.
- + Success measured in shipped product, not tickets.
2.0 / Wordmark
- 1.1 Introduction
- 1.2 Our Studio
- 1.3 Services
- 2.1 Position
- 2.2 Opportunity
- 2.3 Solution
- 2.4 Process
- 2.5 Proof
- 3.1 Case Study 1
- 3.2 Case Study 2
- 4.1 Metrics
- 4.4 Metrics
- 4.5 Metrics
- 5.3 Creative Team
- 5.4 Team Expanded
- 6.1 Packages
- 6.2 Testimonial
- 6.3 Investment
Queto
METRICS
deploys mo / production traffic
2.1M
teams running techside in production
55K
global edge regions
12
Number of daily writes
72K
Audience · role
Traffic by device
Total req / 2026
3B
Audience · gender
ENGINEERS
Top traffic cities
SAN FRANCISCO33%NEW YORK22%BERLIN11%LONDON7%TOKYO4%
METRICS
(Active developers monthly)
254k
(Adoption · YoY)
↓ (Image description / credit)
↓ (Image description / credit)
RUNFORM — DEX
2024
Summary
Runform migrated 14 microservices, two Postgres clusters and their entire observability stack onto Queto in nine weeks. P95 latency dropped from 380ms to 92ms while their infrastructure bill dropped 41%. The platform team shrank from seven people to three.
Credits
Engineered by
Inés Ferrer & Marcus Tang
Inés Ferrer & Marcus Tang
Link
queto.io/cases/runform
Channels
Changelog
GitHub
Thread
GitHub
Thread
SERVICES
1
Runtime Core
↓ Includes
- Edge compute
- Scheduling
- Workload graph
- P95 SLOs
- Zero-downtime deploys
2
Data Layer
↓ Includes
- Postgres
- Vector
- KV cache
- Object storage
- Replication
3
Observability
↓ Includes
- Metrics
- Traces
- Logs
- Profiles
- Alerting
4
Platform Kit
↓ Includes
- Auth
- Billing
- Audit
- Background jobs
- Webhooks
TEAM FULL STAFF
● INESCEO
● MARCUSCTO
● ADAEZEHead of Runtime
PACKAGES
↓ Starting at
↓ Package name
↓ Includes
$2,400 / mo
Starter Runtime
- AEdge compute · 2 regions
- BPostgres + KV (10GB)
- CObservability core
- DEmail + Slack support
- EUp to 10 developers
$8,800 / mo
Scale Runtime
- AEverything in Starter
- BAll 12 edge regions
- CDedicated compute pool
- DCustom data residency
- EOn-call escalation < 15min
$25,000+ / mo
Sovereign Runtime
- AEverything in Scale
- BSingle-tenant control plane
- COn-prem / VPC deployment
- DQuarterly architecture review
- EMigration team embedded
↓ (Testimonial)
6.2 the clarity of the runtime, the strength of the operator story, and the quality of execution have made techside the only piece of infrastructure we don't argue about anymore.
INVESTMENT
↓ (Series B)
we're raising $42m for 18% equity to fund hiring across runtime engineering, platform reliability and operator education.