For people who build with AI
The infrastructure agents
already know how to run.
Your agent already writes the app. Here it also puts it live: sign-in, deploy, data, billing, on-demand code, monitoring and email, from the first address with HTTPS to the first paying customer.
Seven MCP servers live, four light tools in each, OAuth 2.1. Free to start, no card. The dashboard is in Portuguese for now.
Where to start
Where is your app stuck?
Pick the sentence that is yours: the piece that solves it is right below.
Hoster
My app works, but only on my machine.
Ask your agent to publish it: you get an address with HTTPS, and your own domain comes later.
See Hoster
Monitors
I want to know when my site goes down.
With Monitors, your status page stays up, checked nonstop.
See Monitors
Messages
My emails land in spam.
With Messages, your domain sends with SPF, DKIM and DMARC set up right.
See Messages
Auth
People need to sign in to my app.
Sign-in with a code by email, organizations and roles, ready to use. Your agent can sign in too, with a human step in plain view.
See Auth
The proof
This line runs on its 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, with no cookies.
The line's blog
Published on Blogs, from the Marketing line.
Dashboard sign-in
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.
Live now
Everything Between the Idea and the Paying Customer
Between your idea and a product that charges, there are always the same pieces: sign-in, deploy, data, billing, on-demand code, monitoring and email. We built each one because we got tired of rebuilding them. Each one works on its own, without requiring the others.
Your Agent Runs the Infra. You Review.
All seven products speak Model Context Protocol over the official SDK, with OAuth 2.1 and the same sign-in, and all in the same way: four tools (the guide, read, write and delete) that do everything the dashboard does. Delete, revoke or cancel only happens after your yes, in the conversation.
One endpoint, nothing to install
The servers are remote: no npm package and no local process to maintain. You point Claude, Cursor or VS Code at your project URL and the catalog shows up.
OAuth 2.1, not a key in .env
The agent signs in as you, with your role. Tokens are validated by audience: a token for one product does not work on another. No API key pasted into a prompt.
The docs the AI reads first
Each product publishes an llms.txt with the full catalog, the errors and what does not exist, so the agent does not invent the call that will fail. Six also publish an llms-mcp.txt just for the MCP server; Hoster documents its server inside its own llms.txt.
Writing has brakes, on purpose. Deleting a project in Hoster requires explicit confirmation; Functions and Monitors delete nothing through MCP; sending email in Messages requires an idempotency key and has a daily cap. Creating and editing users or organizations stays in the dashboard and the REST API. Structural writes with no human watching are not a convenience. They are an incident.
Create the Account, Point, Run
No onboarding process, no discovery call, no waitlist. The path to the first result is the same on all seven products.
01
Create the account, get the key
One account, one key, right away. No AWS account, no Docker to spin up, no card at the door.
02
Point it at your project
One line of configuration or a curl. Or, if your agent is doing the work, the MCP URL, and OAuth handles the rest. No account yet? The agent creates its own: you just read a code in your email.
03
Run it
The first authenticated user, the first site live, the first function responding or the first email delivered. Today, not next sprint.
One Person Now Does What Used to Take a Company
Not because people got faster. Because the part that took a whole team (writing the code, setting up the infra, connecting the pieces) became a conversation with an agent that works all day.
The team became an agent
What used to take a development team now fits in a conversation. Whoever has the idea carries it out.
Scale stopped being expensive
You do not need to raise money to put a product into the world. The first project on each piece is free, no card.
Operations belong to the agent too
Publishing, storing data, signing in, charging and monitoring: your agent does it, in the same conversation. You review.
One person, one idea and one agent. What is missing is where all of it will live. That is the part we build.
The infrastructure agents already know how to run
All seven products speak MCP: four light tools that do everything the dashboard does. Your agent creates, publishes and rotates keys; deleting, revoking or charging waits for your yes.