pendpost
Summary
Standard post schedulers assume a human wrote every caption — the moment an AI agent is doing the drafting, there's nothing stopping it from publishing unreviewed copy straight to your brand accounts. Pendpost is built around that gap: the agent drafts, you clear the gate, then it ships.
The core workflow runs locally on 127.0.0.1 — no credentials sent to a third-party cloud, secrets stay in your own .env, and the process starts in mock mode so you can walk the full loop before connecting a single account. The approval gate is a dial: start by signing off on every post, then selectively enable auto-approve per platform as trust builds, until the agent is running your social presence around the clock and you only step in by exception. A circuit breaker trips on Meta action blocks and halts publishing until you clear it, which is the kind of failure mode a plain scheduler ignores. Where it breaks: teams needing a visual content calendar, collaborative multi-user workflows, or non-technical operators who can't run a local Node process will hit a ceiling fast.
Bottom line: Pick this if you're a developer or technical solo operator who wants an AI agent drafting across a dozen platforms with a hard approval layer you own — plan something else if your team includes non-technical stakeholders who need a browser-based interface without touching a terminal.
Pricing Plans
Subscription- Free Tier
- Unlimited posts and brands when self-hosted; cloud requires paid plan
Free / Self-host
Full MIT app, self-hosted, unlimited posts and brands
- Unlimited posts
- Unlimited brands
- Self-hosted only
Starter
24/7 publishing for one brand, 50 posts/month
- 1 brand
- 50 posts/month
- 5 GB storage
Studio
24/7 for up to 5 brands, 300 posts/month, team roles
- Up to 5 brands
- 300 posts/month
- 25 GB storage
- Team roles
Agency
24/7 for up to 20 brands, 1200 posts/month, client audit records
- Up to 20 brands
- 1200 posts/month
- 100 GB storage
- Auditable records
View full pricing on pendpost.com →
Pricing may have changed since last verified. Check the official site for current plans.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Runs entirely on 127.0.0.1 with secrets in your own .env, so your account credentials never leave your infrastructure — which means you're not trusting a third-party cloud with the OAuth tokens for every platform you manage.
- The approval gate is recorded per actor, separating who drafted from who approved, so you have an auditable answer when a client asks why a specific post went live.
- A circuit breaker halts publishing when Meta returns an action block, so a misconfigured campaign stops automatically instead of burning your account's standing while you sleep.
- MIT-licensed self-hosted core, so you're not locked into a vendor's pricing changes or deprecation timeline for the foundational workflow.
- Caption linting runs against editable rules before any post can publish, which means brand-consistency errors get caught before they reach the approval queue rather than after they've shipped.
Cons
Sign in to edit- Setup requires running a local Node process via CLI — non-technical team members or clients who expect a browser login cannot operate the tool without a developer intermediating, and teams with mixed technical audiences end up maintaining a separate interface layer or hand-holding every approval.
- There is no visual content calendar, drag-and-drop scheduling grid, or native multi-user dashboard; teams that do content planning collaboratively across roles will find the approval queue insufficient and move to a hosted social media management platform that offers those surfaces.
- The self-hosted path puts infrastructure maintenance, uptime, and platform credential rotation on the operator — teams that need always-on publishing without managing a local server are pushed to the paid cloud tiers, at which point the cost-and-control argument for self-hosting dissolves.
- No public API is exposed from the local install per the validator context, which means integrating pendpost into an existing internal toolchain or triggering agent runs from external systems requires direct process-level integration — teams building multi-system pipelines will find this a hard blocker and reach for an alternative with a documented HTTP API.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Instagram, Facebook, LinkedIn, YouTube, X, Telegram, Discord, Nostr, Mastodon, WordPress, Ghost; beta: Reddit, Pinterest, TikTok, Google Business Profile
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-07-08T21:06:29.108Z
Best For
Who it's for
- Solo operators wanting local control
- Teams needing auditable approval workflows
- Users managing multiple brands or clients
What it does well
- AI-assisted drafting and scheduling of social posts
- Multi-platform publishing with human approval gate
- Self-hosted always-on social media management
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare pendpost
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is pendpost free?
- pendpost has a permanent free tier alongside paid upgrades. You can keep using a baseline version indefinitely without paying.
- Is pendpost open source?
- No — pendpost is a closed-source tool. Source code is not publicly available.
- Can I self-host pendpost?
- Yes. pendpost supports self-hosting on your own infrastructure.
- What platforms does pendpost support?
- pendpost is available on: Instagram, Facebook, LinkedIn, YouTube, X, Telegram, Discord, Nostr, Mastodon, WordPress, Ghost; beta: Reddit, Pinterest, TikTok, Google Business Profile.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Most post schedulers were designed for a world where a person writes the caption, picks the time, and presses send. Pendpost is designed for the opposite case: an AI agent drafts and schedules posts across Instagram, Facebook, LinkedIn, YouTube, X, Telegram, Discord, Mastodon, Nostr, WordPress, and Ghost, while every post sits in a draft queue until a human explicitly approves it or auto-approve is enabled per campaign. The vendor describes the process as ‘agent drafts, you approve, then it ships’ — with the explicit constraint that an agent cannot grant itself autonomy; only the operator can enable auto-approve.
The differentiating feature is the audit trail baked into that gate. Drafting and approving are recorded as separate actor steps, so there is always a traceable answer to ‘who approved this post.’ The caption linter runs against editable brand rules before anything can publish, and the Meta circuit breaker halts outbound sends when the platform starts blocking — behaviors that a queue-and-fire scheduler does not have.
Pendpost fits developers, agencies managing multiple client brands, and technical solopreneurs who want local control over credentials and a clear record of what shipped and who cleared it. It does not fit teams that need a visual drag-and-drop content calendar, non-technical editors who cannot operate a CLI, or organizations that require a hosted multi-user dashboard with role-based permissions. The MIT-licensed local-first core is self-hostable; cloud tiers are paid-only features for teams that want to skip the local setup.
The tool ships with an MCP server alongside the core agent, and the vendor states an API is described in the docs. Setup starts with `npx pendpost`, runs in mock mode by default so credentials are never required to test the full approval loop, and binds exclusively to 127.0.0.1 — nothing phones home from the local install.