Umbra Group / Studio / Cases
← Studio

Studio / Cases

§ Studio in production · The receipts

Cases.

Live reference deployments. The work, the metrics, the receipts — what the Platforms library does when it's actually operating, not what we promise it could do.

CASE · 01 Editorial publishing platform · Umbra Group property Live since 2024 · operated by Atlas since 2026 · LATAM Forward Deployed Engineering flagship

The full stack, operating on our own property.

An editorial publishing platform we own and operate under Umbra Group, used as the lighthouse case for the Platforms library. Every Studio platform is deployed against this site in production — and the receipts are visible in the public sitemap.

VerticalEditorial publishing
StackAtlas + 6 executors
ModeWatch · operated by Studio
SustainedMonths, no slips

The problem

An editorial property publishing daily across SEO-driven verticals, with growth bottlenecked by manual work: schema audits, metadata maintenance, entity coverage, multi-channel distribution, weekly recaps. Every additional article meant additional human hours — a linear cost curve against a content business that needs to be sub-linear.

The diagnosis

Pulso mapped seven workflows that were eating the week. Five were structurally similar across the corpus — pattern candidates. The other two were one-off and got descoped. Output: a Sprint scoped to deploy six executor platforms plus the Atlas cockpit, with the operator stepping out of the day-to-day after handoff.

Live receipts

  • 100% schema coverage across 1,800+ posts, sustained since deployment. Every new publish gets schema; every edit re-syncs.
  • 240+ entity hub pages live, each with biography, identity links, and full cross-link graph back to articles that mention them.
  • 24+ durable workflows operated by Atlas under a single cockpit, with per-function cost and latency traced.
  • Three distribution channels live with per-channel recovery — zero dropped posts across the deployment.
  • Weekly recap shipped every week without exception since deployment. The cadence has not slipped.
  • Zero engineering tickets raised for SEO or schema work since the platform went live. The function is operated, not staffed.

Source — Internal observatory + live-site audit · 2026-05

What the operator stopped doing

Quarterly schema audits. Manual metadata rewrites. Hand-curated landing pages for new entities. Cross-posting across social channels every publish. Friday-afternoon recap scrambles. Reading every alert from market-monitoring tools. The operator now reads a single morning brief from Atlas and decides where to spend judgment.

02 In the pipeline

Reference deployments we're documenting next as Studio expands. Brief teasers below; full case studies follow once metrics stabilize.

Case · 02 · Coming

Music community platform

A 281K-member online community where Studio operates the editorial calendar and per-channel distribution stack.

Case · 03 · Coming

Independent artist services

An automated press & promotion bureau for independent artists — Pulso, Sprint, and ongoing operation with the same Platforms library.

Case · 04 · Open

Your workflow

Studio runs two Sprint engagements at a time. If your workflow is a fit, Pulso is how we find out together.

03 Want to see one live?

We run a 30-minute walkthrough on the live reference deployment.

The morning brief from Atlas, the schema audit catching a deliberately broken page, a multi-channel distribution event firing, and a Cowork delegation handoff — end to end on production data, no slides.