The fleet ledger ✳ Cloudproc
Know what your fleet is actually running.
Not another APM clone. Cloudproc keeps the record straight — every instance reports its live configuration and the application-level metrics that matter, into one ledger you can read at a glance.
Free trial · no credit card · no agents to install
- api-gatewayprodlog_level=infoworkers=12gzip=onv4.1.0
- payment-svcprodtimeout_ms=800retries=3log_level=warnv2.3.1
- worker-poolprodprefetch=32queue=highheartbeat=10sv1.9.2
- search-apistagingreplicas=2cache=warmlog_level=debugv0.7.4
- email-relayprodrate_cap=50/stls=strictretries=2v3.0.0
Sect. 01 — Contents
Built for teams running real services.
A small, opinionated tool for the boring but load-bearing question of what is actually running.
- № 01
Configuration Governance
Every running instance pushes the configuration it is actually using, grouped by subsystem. See what is deployed, where, with what settings — across every service in your fleet.
PUSH — LIVE CONFIG - № 02
Lightweight Application Metrics
Push the application-level numbers that matter — counts, gauges, timings — without setting up a full APM stack. Simple to send, easy to read.
COUNTS · GAUGES · TIMINGS - № 03
Multi-Tenant Hierarchy
Organisations, projects, services, and instances — with the boundaries teams actually need. Clean separation between environments and squads, no shared blast radius.
ORG → PROJECT → SERVICE → INSTANCE - № 04
A Single Dashboard
One web dashboard for everything you run. Browse your organisations, drill into a service, inspect an instance — all from the same place.
ONE PANE, NO TABS - № 05
Language-Agnostic Ingest
Any service that can make an HTTP request can talk to Cloudproc. No proprietary SDKs to vendor in, no agents to babysit — just push JSON when you have something to say.
HTTP + JSON — NO SDK - № 06
SaaS — No Infra to Run
Hosted, managed, and ready in minutes. No control plane to operate, no storage to provision — point your services at the ingest endpoint and you are live.
HOSTED & MANAGED
Sect. 02 — The wire
If it can make an HTTP request, it can report.
One endpoint, plain JSON. Each instance pushes the configuration it booted with — upserted by name and group — and any numbers worth keeping. No SDK to vendor in, nothing to sideload next to your process.
Read the documentation$ curl -X POST /v1/instances/ingest \
-H 'X-cloudproc-instance-session: •••' \
-d '{
"configurations": [
{ "group": "runtime",
"name": "log_level",
"value": "info" },
{ "group": "runtime",
"name": "workers",
"value": "8" }
]
}'
← 200 { "status": "ok" } · 2 upsertedOpen the ledger
Start the record.
Point your services at the ingest endpoint and the ledger starts filling in.
Free trial — no credit card · cancel anytime