Platform APIs change under you
Meta versions its Graph API every few months; X and LinkedIn have both replaced theirs. Keeping direct integrations alive costs 9–17 weeks of developer time a year — on Postproxy that's our team's job.
Ten clients or three hundred — easy to start, easy to switch.
Clients connect their own accounts through a link — no passwords, no app reviews — and the first post goes out the same day.
At that scale, publishing is an engineering problem. You're pushing thousands of posts a week through eleven platform APIs — each with its own rules, limits, and changes — while keeping every client's accounts strictly separate.
Meta versions its Graph API every few months; X and LinkedIn have both replaced theirs. Keeping direct integrations alive costs 9–17 weeks of developer time a year — on Postproxy that's our team's job.
In a shared dashboard, a post or comment reply lands on the wrong client with one bad click. Postproxy scopes every account, post, and reply to its client's profile group, so cross-posting to the wrong brand isn't possible.
A few posts a week across several platforms for 300 clients adds up to thousands of posts, plus the comments and DMs they trigger. That volume needs proper engineering.
Postproxy handles the whole client workflow at the infrastructure level, so your team focuses on client work, not token management and API plumbing.
One profile group covers all of a client's social accounts (Instagram, LinkedIn, TikTok) in one place, under one scope.
Schedule a week ahead for every client. Each post gets a clear status — and if publishing fails, the reason why — without logging into any network.
Create posts as drafts. A draft never publishes on its own — someone reviews it, then publishes it from the dashboard or the API.
Pull engagement metrics, reach, and post outcomes back per client. Build reporting dashboards without logging into each network.
Surface incoming comments, direct messages, and platform reviews across all client accounts, and respond through the same API.
Use the dashboard, call the API, drop in an n8n node, or use the MCP server in your AI workflow. Works with whatever your team already has.
Add a client, pay a few dollars more. The price per client drops as you grow.
One bill for the whole roster. A new client can connect and publish the same day. When a platform changes its API, that's our problem, not yours.
10–21 weeks to build, plus 2–6 weeks of app review. Then 9–17 weeks of a developer's time every year to keep it running.
See pricing and calculator → What building in-house actually costs →
Every client lives in their own profile group. Connected accounts, posts, comments, and insights are scoped to that group — nothing crosses over to another client, and offboarding a client means removing one group.
Create a profile group per client and share a reconnection link. Book a call — we'll walk you through the migration.
Postproxy is the perfect interface between our internal tools and Meta and LinkedIn. People underestimate how much effort it takes to keep those connections running smoothly – Postproxy just handles it.
Postproxy runs on European infrastructure, handles credentials the way you'd want your own handled, and is built to meet the highest compliance and security standards.
Your data is protected by enterprise-grade encryption, secure APIs, and strict access controls designed to keep everything safe.
All data is stored and processed on European servers, ensuring sovereignty, reliability, and compliance with local regulations.
GDPR-compliant today and currently obtaining our SOC 2 Type II certification. We build Postproxy to meet the highest standards for privacy, security, and transparency.
If you manage social for more than one brand (publishing, reporting, or engagement), Postproxy can be the infrastructure layer. These are common patterns, not a closed list.
Full-service shops managing 10–100 brands. One API for publishing, insights, comments, DMs, and reviews. One billing line, isolated scope per client.
Internal teams serving multiple business units. Keep each department's accounts, content, and inbox separate without extra tooling.
Products that offer the social workflow as a feature under your brand. Clients connect accounts through your product; Postproxy stays behind the scenes.
Consultants who outgrew a single scheduler. Manage publishing, reporting, and client inboxes independently as the roster grows.
You pay per client. The Business plan is $49/month and covers 20 clients. Extra clients cost $2/month each up to 50, $1.75 up to 100, $1.50 up to 250, and $1.25 beyond that. Examples: 30 clients ≈ $69/month, 50 clients ≈ $109/month, and Enterprise covers 300 clients for $399/month with $1 per client over that. The pricing page has a calculator for exact numbers.
You request a connect link from the API and send it to the client. They open it, authorize their own accounts, and the profiles land in their profile group. No passwords change hands, and your team never handles client credentials. See the profile groups docs.
Yes, through drafts. Create a post as a draft and it never publishes on its own — someone reviews it and publishes it from the dashboard or the API. See the posts reference.
Yes. Postproxy is an API, so your clients only ever see your tool or portal — connect links open from inside your product. See Postproxy for SaaS or the white-label guide.
Instagram, TikTok, LinkedIn, X, YouTube, Facebook, Threads, Bluesky, Pinterest, Telegram, and Google Business. Platform-specific details are in the platform docs.
Yes. Postproxy publishes through each platform's official API with verified app credentials — accounts connect through the platform's own authorization screen, and no app review is required on your side.
Ten clients or three hundred, every one isolated in its own profile group — one integration, one bill, ready from day one.