Embed publishing in your SaaS

We handle the platform layer.

Ship posting across major networks from your product, without your team owning every integration, review cycle, and delivery edge case.

Reality check

"We'll just build it ourselves"

Sounds reasonable until the first review cycle. Then the second. Then someone is maintaining tokens instead of shipping features.

Platform reviews take weeks

Every network has its own app registration, scope review, and policy rules. Multiply by the number of platforms you want to support.

Ops work piles up fast

Tokens expire, delivery fails silently, rate limits differ per platform. Someone has to own that layer — and keep owning it.

Your roadmap pays the price

Each integration adds maintenance surface. Before long the team is running a side product instead of building what users actually pay for.

Platform layer

We run the integration layer

Postproxy handles platform integrations, OAuth, token lifecycle, and delivery—so your team ships product features instead of maintaining every network by hand.

Platform integrations

One API surface. Platform maintenance and re-certification stays on our side.

OAuth, tokens, delivery

OAuth, token lifecycle, and delivery handled at the infrastructure level. You get webhooks, not incidents.

Platform API changes

We absorb upstream changes. Your integration keeps working when a platform updates its API.

Roadmap focus

Ship the feature your users want. The platform layer does not compete for your sprint.

EU-hosted infrastructure

Data stays in the EU. Compliant by default for privacy-sensitive markets and enterprise contracts.

Multi-account publishing

Publish across hundreds of end-user social accounts from a single integration. No per-account complexity on your end.

Inside your product

User scope from your API

No Postproxy signup for your customers. Provision from your servers, run OAuth from your UI, change access when your model changes.

Create and connect social accounts inside your app.
Webhooks for delivery, failures, and when a user must reconnect before posts fail. No polling.
Publish from your own app whenever your product logic says so. No extra hop through our UI.

FOR DEVELOPERS

Built for how developers actually work

Everything you need to plug into any project and start publishing right away. Built by developers, for developers.

Here are all the docs bundled and ready for your tools. Feed it to Claude Code, Cursor, or your agent of choice

POST /api/posts

curl -X POST "https://api.postproxy.dev/api/posts" \
     -H "Authorization: Bearer YOUR_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "post": {
         "body": "Hello World!",
         "draft": true
       },
       "profiles": ["facebook", "instagram"],
       "media": ["https://example.com/image.jpg"]
     }'

import PostProxy from "postproxy-sdk";

const client = new PostProxy(
  "YOUR_API_KEY"
);

await client.posts.create({
  content: "Hello World!",
  profiles: ["twitter"],
});

TypeScript

from postproxy import PostProxy

client = PostProxy("YOUR_API_KEY")

client.posts.create(
  content="Hello World!",
  profiles=["twitter"],
)

Python

require "postproxy"

client = PostProxy::Client.new(
  "YOUR_API_KEY"
)

client.posts.create(
  content: "Hello World!",
  profiles: ["twitter"]
)

Ruby

import postproxy "github.com/
  postproxy/postproxy-go"

client := postproxy.New(
  "YOUR_API_KEY",
)

client.Posts.Create(ctx,
  postproxy.PostCreateParams{
    Content: "Hello World!",
  },
)

import dev.postproxy.PostProxy;

PostProxy client = new PostProxy(
  "YOUR_API_KEY"
);

client.posts().create(
  PostCreateParams.builder()
    .content("Hello World!")
    .build()
);

Java

using PostProxy;

var client = new PostProxyClient(
  "YOUR_API_KEY"
);

await client.Posts.CreateAsync(
  new PostCreateRequest {
    Content = "Hello World!",
    Profiles = ["twitter"]
  }
);

.NET

use PostProxy\PostProxy;

$client = new PostProxy(
  "YOUR_API_KEY"
);

$client->posts->create([
  "content" => "Hello World!",
  "profiles" => ["twitter"],
]);

PHP

If you're using a language we don't support yet, let us know.

POST /api/webhooks

curl -X POST "https://api.postproxy.dev/api/webhooks" \
     -H "Authorization: Bearer YOUR_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "name": "Production status updates",
       "url": "https://yourapp.com/webhooks/postproxy",
       "events": [
         "post.processed",
         "platform_post.published",
         "platform_post.failed"
       ],
       "secret": "whsec_your_signing_secret",
       "active": true
     }'

REST API

Simple HTTP endpoints. Send a single request with your content and platform list — we handle format conversion, auth, and per-platform delivery.

SDK

Official SDKs for TypeScript, Python, Ruby, Go, Java, .NET, and PHP. One client, all platforms — integrate in minutes.

Webhooks

Get notified when posts are published, failed, or retried. Build dashboards, trigger workflows, or sync status back to your system.

INFRASTRUCTURE

Serious about where your data lives.

Postproxy runs on European infrastructure, handles credentials the way you'd want your own handled, and is GDPR-compliant without you having to think about it.

SECURITY

Security at core.

Your data is protected by enterprise-grade encryption, secure APIs, and strict access controls designed to keep everything safe.

HOSTING

Europe hosted.

All data is stored and processed on European servers, ensuring sovereignty, reliability, and compliance with local regulations.

COMPLIANCE

GDPR-compliant.

Built to meet Europe's highest privacy standards, Postproxy processes and stores data with full compliance and transparency.

Blueprint

Start from something real

We built a small reference project - it's showcasing how Postproxy is meant to be implemented in a real product. Treat it as a map: less trial and error than inferring everything from the API reference alone.

Potato

Next.js + Supabase + Postproxy in one place.

Initializing connection from your UI
Managing profile groups and how to scope them for your customers
Posting end to end

View Potato on GitHub Watch the walkthrough

Potato blueprint app — Acme Corp calendar with scheduled posts

Where it fits the best

Typical SaaS shapes

If your product needs publishing to social, Postproxy can slot in there. These below are common use cases, not a closed list.

Agency SMM products

Your own client workspace for brands and campaigns. Publishing stays in your product, not a generic scheduler on the side.

AI content platforms

Generated copy and assets go out from the same flow. No export step and no second tool just to hit the networks.

CMS and editorial stacks

Articles, releases, and site updates become posts from the system that already owns the content.

Vertical and industry SaaS

Social is part of the job for your ICP. Embed publishing next to scheduling, CRM, or lifecycle features they already pay for.

Ship the feature, not the platform project

Publishing inside your product — without a second team maintaining integrations.

Get started Talk to founders