Give each client a workspace with their own channels, library and calendar. Your team moves between them in a click, and nothing posts twice.
Free planEvery major networkOpen source
This week
MarchRun every client from one place, and grow without growing the busywork.
Channels, calendar and library, kept apart for each client.
Clients approve posts in their own portal, on Cloud.
Roles for everyone who touches a post.
An AI agent drafts posts; your team keeps the final say.
Plan it, write it, check it and send it, without switching apps.
Each client has a workspace of their own. Jump between them from the bar, with every calendar, channel and file exactly where you left it.
Workspaces
3 clientsEvery workspace keeps its own media library, so one client's photos never end up in another's post. Tags find things fast, and the assistant writes missing alt text when you ask.
Connect an AI agent through the API or MCP server. It drafts and checks posts for each client, and nothing goes out until a person approves.
Tidepool 2.0 is live: offline mode, home-screen widgets and a calmer dark theme.
Tidepool 2.0 is live: offline mode, home-screen widgets and a calmer dark theme.
Write it yourself, or let your agent, your code or a feed send it. Each post is checked, then sent once through the network's official API.
Plan, write, schedule and see results for every network from one calendar.
Let Claude or any MCP agent draft and schedule posts, with your approval.
Run it on your own server or let us host it. Your posts and data stay yours.
Connect your accounts and schedule your first post in a few minutes.
Yes. Give each client a workspace with its own channels, calendar, library and team.
Yes, on PostLoop Cloud: multi-step approvals and a client portal where clients review without needing a seat.
Yes. The open-source edition is free to self-host, including for clients. If you change it and run it for others, you share your changes under the same licence.
White-label, with your own domain, logo and colours, is part of PostLoop Cloud.
Network tokens are encrypted at rest with envelope encryption, never logged and never returned by the API. Every workspace is kept apart by the database itself.