Operations is how you run what already exists

Know what happens in what you put online.

Where each visit came from, how far each video was watched, what each agent did and what it expects from you. No cookie in the visitor's browser, no progress bar that fakes duration, and no server to set up for measuring.

Same login across the line's dashboards. A code arrives in your email; you paste it once. The dashboard is in Portuguese for now.

Where to start

What is still slipping past you?

Pick the sentence that is yours. The piece that solves it is right below.

Still choosing? Start with the line's guides

Cookieless site analytics: what you can measure and what you cannot
How to know how far each video was watched
How to create a UTM link to know where each visit comes from
See all guides on the blog (in Portuguese)

The proof

This line runs on the house's own pieces.

It is not a showcase. It is Ciro's own operation, right here. If a piece breaks, it breaks for him first.

This site

Published by Hoster, from the Infrastructure line.

This site's visits

Measured by Analytics, from the Operations line, without cookies.

The line's blog

Published on Blogs, from the Marketing line.

The dashboards' sign-in

A code by email through Auth, from the Infrastructure line.

Ciro's letters

Sent by Newsletter, from the Marketing line, only to people who confirmed.

Ciro's agents

They work in Assistant, from the Agents line, and ask for his yes before anything that cannot be undone.

On the same line

See, Measure and Delegate What Is Already Live

Each one handles one part of running what already exists, and each one opens on its own, without requiring the others. All four are live.

For the agent

The Agent Reads. You Decide.

Each product tells the agent what it can do, and what stays with a person.

The documentation the agent reads first

Each product has an llms.txt with the full documentation: the script, the routes and what it does not do. So the agent does not invent a call that will fail.

The agent does what the dashboard does. Deleting is up to you.

Videos has an MCP server with four light tools: upload, edit and publish through the same routes as the dashboard. Deleting waits for your yes, in the conversation.

Empty is not zero

In Analytics, without measurement, the number stays empty. What was not measured never shows up as zero, for the agent or for you.

The first number

Sign In, Paste, Check

There is no onboarding and no discovery call. The path to the first result is the same in every product.

01

Sign in with a code

No password to create. A code arrives in your email. You paste it once, and the session works across the line's dashboards.

02

Paste one line

The Analytics script in the <head>, or the player script where the video will live. Or paste the prompt into your agent.

03

Check

The site goes from "Waiting" to "Receiving" when the first visit arrives. The video plays when the first quality is ready.

MCP

Built for Your Agent, From Day One

Connect your agent to Analytics and Videos, and it runs the whole line with your login.

Four tools

The guide, read, do and delete. Light, so context is left for the work.

Everything the dashboard does

Create, edit, publish and rotate keys, through the same routes as the dashboard.

Deleting waits for your yes

Delete, revoke or cancel only happens after your yes, in the conversation.

Connect your agent

Each product's MCP address is in the line's llms.txt.

The Questions, in the Order They Come Up

Know what happens in what you put online.

Analytics shows where your visitors come from. Videos shows how far each video was watched. Same login for both.