Postproxy
Postproxy is a unified social media API that lets agencies, SaaS products and AI agents publish posts, handle comments, direct messages and reviews across eleven networks from a single integration, on EU-hosted infrastructure.
What is Postproxy?
Postproxy is an integration layer that replaces per-platform social media work with one API. Instead of registering, certifying and maintaining a separate app for each network, a team sends a single payload and Postproxy maps it to each platform's rules, returning a per-platform outcome. Eleven networks are covered — Instagram, Facebook, Threads, TikTok, X/Twitter, YouTube, LinkedIn, Pinterest, Bluesky, Telegram and Google Business — with Reddit announced.
Its scope goes well beyond posting. The same contract handles the full engagement flow: reading and replying to comments, sending and receiving direct messages, fetching and answering Google Business reviews, and pulling post and profile statistics normalised across networks. Platform quirks are absorbed on the vendor's side, from Instagram Reels, Stories and collaborators to YouTube Shorts and thumbnails, TikTok AI-content flags, LinkedIn company pages, Pinterest boards, Bluesky's AT Protocol plumbing, a bring-your-own Telegram bot and multi-location Google Business posts.
Three audiences are addressed explicitly. SaaS products embed the workflow white-label: a scoped environment is provisioned server-side per customer, who connects accounts through the vendor's own interface and never creates a Postproxy account. Automation and agent builders get a native MCP server, a one-click Claude connector, an installable skill, and verified n8n, Make and Zapier integrations. Agencies get scheduling queues and profile groups that keep each client's posts, comments and messages strictly separate.
Developer tooling is substantial: official SDKs for Node, Python, Ruby, Go, PHP, Java and .NET, webhooks with delivery tracking, automatic retries with back-off, idempotency, full publish logs, historical post import, an interactive playground and a sandbox mode. Billing rests on the profile group, meaning one brand, client or publishing setup holding up to eleven connected profiles.
Behind it is 64Bit Labs UG, a Berlin company run by two founders with prior experience at Mimi Hearing Technologies, Staffbase and Adjust. Infrastructure is clustered and European, with claimed response times around 35 ms, 150 ms at the 95th percentile and 99.96% uptime. GDPR compliance is claimed; SOC 2 Type II remains in progress.
What it does
- Publish a single payload to eleven social networks through one API call
- Reply to comments and direct messages, and answer Google Business reviews, from the same API
- Schedule posts into named queues with weekly recurring slots and per-group timezones
- Let an AI agent publish and engage over MCP from Claude, ChatGPT, Cursor, Codex, Hermes or OpenClaw
- Pull post and profile insights back, normalised across every connected network
- Provision a scoped, white-label environment per customer so end users never see Postproxy
- Trigger publishing from n8n, Zapier or Make without writing code
When to use Postproxy / When not to
A quick filter to help you decide if Postproxy is the right fit.
When to use Postproxy
- SaaS teams that want publishing, comments and DMs inside their own product, where end users never create a Postproxy account
- Developers who would rather maintain one REST integration than eleven separate social platform integrations
- Builders of AI agents and automations that publish over MCP from Claude, ChatGPT, Cursor, Codex, Hermes or OpenClaw
- Agencies running many client brands who need scheduling queues and strict separation between client accounts
- No-code automators wiring social publishing into n8n, Zapier or Make workflows
When not to use Postproxy
- Anyone after a content creation or copywriting tool: Postproxy distributes content, it does not generate it
- Teams that need paid social advertising, since only organic publishing and engagement are covered
- Users expecting a mobile app or a polished all-in-one social suite rather than an API and a developer dashboard
- High-volume publishers on X/Twitter, capped by default at 20 posts per 24 hours per account
- Organisations that require a completed SOC 2 certification, a contractual uptime guarantee or a named subprocessor list today
How to use Postproxy
A typical end-to-end flow, from setup to results.
- Create an account on the Postproxy dashboard; no credit card is required
- Open the API keys settings and create a key, either full-access or scoped to a single profile group
- Pass that key as a Bearer token on every request
- Open Profiles in the dashboard and authorise the networks you want through OAuth
- Note that a first profile group is created automatically, and each connected account becomes a profile inside it
- To onboard end users programmatically, call initialize_connection on a profile group and redirect them to the OAuth URL it returns
- Choose a publishing route: the REST API, the MCP server for agents, or a no-code tool such as n8n, Zapier or Make
- For Claude Code, register the hosted MCP endpoint with your API key in one command; for Claude desktop, web or ChatGPT, connect from the directory or paste the connector URL
- Rehearse safely in the interactive playground and sandbox mode before going live
- Publish, then consume webhooks and publish logs to confirm what actually happened on each platform
Pros & Cons
Pros
- One integration to maintain instead of eleven, with platform app reviews and API changes absorbed by the vendor
- Publishing, comments, direct messages, reviews and analytics all sit behind the same API contract
- Unusually strong agent support: native MCP endpoint, official MCP registry listing, skills and a one-click Claude connector
- Serious developer tooling, with seven SDK languages, webhooks, retries, idempotency, logs, playground and sandbox
- European hosting and a German publisher, with claimed GDPR compliance and a public trust centre
- Readable, volume-degressive pricing with an on-page calculator and a free tier that needs no card
- Support comes from the founders themselves, including a bookable fifteen-minute call
Cons
- Very young company with a two-person named team, which concentrates real supplier risk
- SOC 2 Type II is only in progress, and the trust centre publishes no documents and no subprocessors
- The terms disclaim any uptime guarantee while marketing pages advertise 99.96% availability
- Liability is capped at the greater of twelve months of fees or 100 EUR, low for a production dependency
- No hosting country or provider is ever named, only European servers
- No support email address is published, there is no mobile app, and the interface and documentation are English-only
- Hard third-party ceilings apply, notably 20 X/Twitter posts per 24 hours per account by default
Pricing & Plans
A free entry point is available: ten posts, with no credit card required. The cheapest paid plan is Agentic at 17 USD per month, billed monthly, including five connected profiles, with additional profiles from 4 USD each and progressively lower unit rates at volume. Two higher tiers follow, Business at 49 USD per month covering twenty connected profile groups and Enterprise at 699 USD per month covering five hundred. Every paid plan includes all features, tiers differing only by billing unit and volume. Prices are displayed in US dollars although the publisher is German, and billing is taken in advance with automatic renewal.
- Free — 10 posts
- no credit card required
- Agentic — 17 USD per month
- 5 connected profiles included
- billed per connected profile
- aimed at AI agents and automations
- Business — 49 USD per month
- 20 connected profile groups included
- billed per group
- aimed at SaaS products and agencies
- Enterprise — 699 USD per month
- 500 connected profile groups included
- for higher volumes and direct support
- Starter 5 posts/hour
- Scale 10 posts/hour
- Enterprise 15 posts/hour
Data, GDPR & hosting
A consolidated view of how Postproxy handles your data.
GDPR overview
Implementation is concrete rather than declarative. Postproxy is operated from the European Union by 64Bit Labs UG (haftungsbeschränkt) in Berlin, named explicitly as data controller, and processing is placed under the GDPR together with German law (BDSG, TTDSG). The privacy policy, last updated 24 June 2026, sets out legal bases article by article — contract Art. 6(1)(b), legitimate interest Art. 6(1)(f), consent Art. 6(1)(a), legal obligation Art. 6(1)(c) — and lists data subject rights from Art. 15 to Art. 21 plus withdrawal under Art. 7(3), exercised at privacy@postproxy.dev. A Data Processing Agreement is available on request. Transfers outside the EU rely on Standard Contractual Clauses or adequacy decisions. No DPO and no Article 27 representative are named, which is consistent for an EU-established company. SOC 2 Type II is only in progress, not obtained.
Who owns the data?
Under the Terms & Conditions, customers keep ownership of every piece of content they publish through Postproxy. The vendor receives only a limited right to process that content for the sole purpose of operating the service, does not pre-moderate it and accepts no responsibility for it; customers remain responsible for their own backups. For personal data, 64Bit Labs UG acts as processor or subprocessor while the customer stays the controller and must hold the necessary rights, legal basis and authorisations. The company states that it does not sell personal data, and reserves only anonymised, aggregated usage data to improve the service.
Reuse rights
The end user keeps full control of their own content and needs no permission from Postproxy to reuse, repurpose or republish it elsewhere, because ownership never transfers. The licence granted to the vendor is deliberately narrow: processing strictly limited to operating the service, which means publishing to the networks the customer instructs, relaying comments, direct messages and reviews, and returning insights. Beyond that, the company reserves only anonymised and aggregated usage data for product improvement. Data reached through connected social accounts is limited to what each feature requires, and the vendor states it does not access unrelated account data. Content published onward remains governed by each network's own terms, which the customer also accepts.
Data retention & training
Hosting summary
The vendor states that all data is stored and processed on European servers, describing its platform as clustered EU infrastructure with multiple server locations, and presents this as a sovereignty and compliance argument. Jurisdiction is unambiguous: the controller is 64Bit Labs UG (haftungsbeschränkt), based at Kolonnenstr. 8, 10827 Berlin, Germany, the terms specify that German law applies with jurisdiction in Berlin, and the privacy policy invokes the GDPR alongside the German BDSG and TTDSG. Beyond the regional claim, however, no hosting country, technical region or infrastructure provider is ever named. Some service providers may sit outside the EU or EEA, in which case the vendor relies on Standard Contractual Clauses or adequacy decisions; no subprocessor is listed by name and the public trust centre shows none. Note that the domain's resolved public IP is a Cloudflare anycast node geolocated in the United States, which reflects the CDN edge in front of the service rather than where application data lives. Anyone with a data residency requirement should ask for the specific hosting country in writing.
Things to keep in mind
Risks and trade-offs to weigh before adopting Postproxy.
- Handing a publishing key to an autonomous agent means a careless prompt can post to a live brand account, so keep key scopes narrow and rehearse in sandbox mode
- A successful API response is explicitly not a guarantee that content was published, stayed live or reached anyone, so build verification in rather than trusting the status code
- Automating volume invites platform enforcement: publishing beyond typical organic patterns may throttle or suspend the underlying social accounts, which are yours to lose rather than the vendor's
- Concentrating eleven integrations behind one very young supplier creates a single point of failure, and liability capped at the greater of a year's fees or 100 EUR will not cover your downside
- Storing long-lived OAuth tokens for every brand account in one place raises the stakes of any breach, however carefully the vendor handles credentials
- Marketing and contract disagree on availability, with 99.96% advertised while the terms disclaim all uptime guarantees, so plan for outages you cannot escalate
- Frictionless cross-posting quietly encourages sending the same message everywhere, eroding the audience-specific judgement that made each channel work in the first place
Setup & Integrations
Technical difficulty
Low to moderate, depending on the route. The no-code path through n8n, Zapier or Make needs no developer at all, and the agent path is close to trivial: one command, or one click in the Claude directory with no API key. The coding path is a standard REST integration, creating a key, passing it as a Bearer token, authorising accounts over OAuth, and leaning on seven official SDKs. The vendor claims a first working integration in under two minutes. A playground, sandbox mode and field-level validation errors smooth the debugging.
Deployment
Integrations
Supported languages
Behind Postproxy
Social
Resources
All the official URLs gathered for verification and reference.
Alternatives
Tools that compete with or complement Postproxy.
Frequently asked questions
How many social networks does Postproxy support?
Is there a free plan?
What is the cheapest paid plan?
Can an AI agent publish through Postproxy?
Can it be used without writing code?
Where is the data hosted?
Is a Data Processing Agreement available?
Who owns the content published through the service?
Is there a minimum age?
How do you reach support?
Should you pick Postproxy?
Postproxy occupies a precise niche: social media infrastructure for people who build things, not another content studio. If the problem is that eleven networks each demand their own app registration, review cycle, token lifecycle, rate limits and breakage handling, this answers it credibly, with one REST contract for publishing, comments, direct messages, reviews and insights, seven SDK languages, webhooks, retries, idempotency, full logs, and a playground and sandbox to rehearse in.
The agentic layer is the part that feels genuinely ahead rather than retrofitted. A hosted MCP endpoint, a one-click Claude connector, an installable skill and a place in the official MCP registry let an agent publish in plain language while platform credentials stay server-side. The white-label path is equally deliberate: your customers connect their accounts inside your product and never learn Postproxy exists.
The reservations concern maturity rather than capability. This is a young Berlin company with two named founders, no published incorporation date and no announced funding. SOC 2 Type II is described as in progress, the trust centre lists no documents and no subprocessors, no hosting country is named beyond European servers, and the terms disclaim the very uptime the marketing advertises while capping liability at the greater of a year's fees or 100 EUR. Third-party ceilings you cannot negotiate away, such as twenty X/Twitter posts a day, remain yours to live with.
The sensible move is to test rather than deliberate, since ten posts cost nothing and need no card. Before committing production traffic, request the DPA, ask which country actually hosts the data, and check the per-platform quotas against your own volume. For an integration you intend to depend on, those three answers matter more than the price.
- Choosing a selection results in a full page refresh.
- Opens in a new window.