A publishing workspace built for people and their agents

Publishing work is spread across drafts, media folders, calendars, social networks, analytics tools, and approval messages. Rolino brings those parts into one controlled workflow. A person can work directly in the web application or authorize an AI agent to prepare the same structured work through the public API, CLI, SDK, or local MCP server.

The product treats drafting, approval, scheduling, and publishing as different actions. Agents can inspect readiness and prepare work without receiving permission to publish. Consequential actions use an exact preview and confirmation so the person can see the destination, content, time, and known blockers before execution.

Rolino is created and operated by Vlad Palacio in Ontario, Canada. The public code is available under the GNU Affero General Public License, and independent teams can review or self-host the application. The managed service at getrolino.com provides the hosted Rolino product and its public developer resources.

Rolino is designed for clear ownership. Workspace members control connected publishing accounts and agent credentials. Existing credentials do not receive new capabilities when Rolino adds a feature. Users must approve added access through the product.

Rolino favors verifiable state over hidden automation. It reports whether a post is a draft, scheduled, queued, delivered, or blocked. It does not treat a queued request as a successful publication. It keeps safe audit records for consequential operations and does not expose provider credentials, bearer tokens, private prompts, or raw provider responses in agent-facing output.

Product questions and feedback are welcome at hello@getrolino.com. Security reports should follow the private process in the project security policy.