Mock proof first
Current screenshot uses local mock mode, not live social credentials.
PostKit
Replace rented schedulers with source you own
Own the social posting system your business depends on.
PostKit is a self-hosted social publisher source package. It gives your team one dashboard, one API, local media storage, scheduled posting, retries, analytics records, and official-API provider boundaries without handing the workflow to another monthly tool.
Use it when a client, operator, or founder already lives in Post Bridge, Buffer, SocialBee, spreadsheets, or Make/Zapier chains and wants the workflow in their own server instead.
1
dashboard
1
REST API
13
modeled platforms
Owner-operated
The buyer runs the server, database, media storage, scheduler, and API keys.
Manual access gate
KapKit talks through fit before checkout, repo invites, or provider work opens.
localhost / postkit dashboard
Workbench tour
Less pitch. More path through the app.
PostKit is easiest to understand as a loop: prove ownership, build the queue, then connect official platform APIs only when the operator is ready.
01 / Owner setup
Run PostKit on your own server.
Paste the owner token, create API keys for automations, and keep the workflow under your own account instead of another rented scheduler.
02 / Compose and queue
Draft once, adapt per platform.
Upload media, choose accounts, create platform-specific versions, schedule posts, publish in mock mode, and inspect target-level results before any live credential work.
03 / Provider boundary
Official APIs or fail closed.
PostKit records missing scopes, credentials, quotas, and app-review blockers instead of pretending a post went live.
What it replaces
The posting workflow should not live in another rented box forever.
Social posting is repetitive, operational, and easy to rent forever. A business needs captions, media, accounts, schedules, retries, provider errors, analytics, and handoff notes. That is a system. If the system matters, owning the source makes it easier to inspect, automate, back up, and adapt.
Post Bridge-style cross-posting and provider API workflows
Buffer-style queues, calendars, channel versions, and scheduled posts
SocialBee-style content categories and evergreen planning
Agency/client posting spreadsheets
Make, Zapier, or webhook automations nobody wants to maintain
One more social scheduling subscription
One source package on your server
Posts trapped inside another SaaS calendar
Drafts, targets, media, and results in your database
Generic cross-posting with unclear provider failure states
Per-target attempts, provider responses, retries, and fail-closed adapters
Manual exports for clients or AI assistants
REST API and API keys for operators and agents
Platform credentials hidden behind the vendor
Buyer-owned official developer apps and OAuth/API credentials
How it works
Mock first. Then connect official providers when the owner is ready.
PostKit lets you learn and verify the workflow before real platform credentials enter the picture.
- 01
Get source access
Start from the KapKit-approved PostKit source package when the launch gate opens.
- 02
Run it privately
Install the Bun + SQLite app, set owner secrets, and open the local dashboard.
- 03
Prove the loop
Create mock accounts, upload media, draft posts, schedule them, publish in mock mode, retry failures, and sync analytics records.
- 04
Connect official providers
Add buyer-owned developer app credentials, OAuth callbacks, scopes, quota access, account eligibility, and platform review evidence where required.
- 05
Operate it
Run the scheduler tick from cron or systemd, inspect provider results, retry failed targets, and automate through API keys.
Platform support posture
Modeled broadly. Published honestly.
PostKit does not scrape passwords, bypass platform rules, hide rate limits, or pretend a post went live. If a provider is missing credentials or approval, it fails closed and records the setup problem.
X / Twitter
Medium
Substack
Instagram
LinkedIn
Facebook Pages
TikTok
YouTube / Shorts
Bluesky
Threads
Pinterest
Google Business Profile
Mastodon
Readiness 1
Mock proof
Prove the posting workflow without touching a real social account.
Readiness 2
Adapter code
Official-API adapter paths can be implemented and tested with mocked HTTP against documented request shapes.
Readiness 3
Live-ready provider
The self-host owner supplies official developer apps, callback URLs, credentials, scopes, quota access, account eligibility, and review evidence.
Readiness 4
Fail-closed unsupported provider
If a platform has no official publishing API, PostKit can model it and explain the blocker without unofficial APIs, cookies, scraping, or browser automation.
Product depth
The source package, dashboard, API, tests, and guardrails.
Owning the workflow means owning the parts that make it operable: source, database, media, credentials, scheduler, results, and the API your operator or AI assistant can use.
Dashboard
Self-hosted UI for owner token setup, account management, compose, queue, results, and analytics.
Server
Bun server and SQLite schema for local-first ownership.
Media
Local media storage so assets stay near the scheduler.
API
REST API for accounts, media, posts, targets, categories, queues, scheduler ticks, results, analytics, and API keys.
Mock proof
Mock provider for safe local proof before real platform credentials enter the flow.
Adapters
Official-API adapter code for the target platform inventory, including X and Medium where official publishing APIs are available.
Substack boundary
Fail-closed Substack posture because Substack's official Developer API does not expose newsletter post publishing.
Provider readiness
Fail-closed provider behavior when credentials, scopes, media rules, or app approval are missing.
Docs and tests
Platform credential docs, provider-readiness docs, smoke tests, and validation tests.
Good fit
Use PostKit when ownership matters.
- Agencies managing repeatable client posting workflows
- Founders who want social operations in their own stack
- Operators who want a dashboard plus API instead of fragile automation chains
- Teams using AI assistants to draft, schedule, inspect, and retry posts
- Businesses that can own server setup and official platform credential work
Not the promise
Do not buy it for magic platform access.
- Teams that want KapKit to host every credential and account for them today
- Buyers who need instant source delivery before the PostKit launch gate opens
- Users expecting unofficial posting, password scraping, or guaranteed app-review approval
Current launch boundary
Manual intake first. No fake launch.
PostKit checkout, source-access delivery, and customer repo invites stay behind explicit launch gates. No production platform credentials are shipped by KapKit. No live third-party publishing verification is claimed from this page. No unofficial Substack private API, browser-cookie, scraping, or browser-automation publishing path is claimed or planned.
The current CTA is manual intake so KapKit can confirm fit, access timing, provider readiness, and the right next step.
FAQ
The honest answers.
Can PostKit replace Post Bridge or Buffer?
For owned drafting, scheduling, media upload, platform-specific versions, API automation, result tracking, retries, categories, and self-host control, yes. For live posting, every platform still requires official credentials, scopes, eligibility, and app-review boundaries.
Is PostKit a hosted SaaS?
No. PostKit is a self-hosted source package. You run it, own the database, store the media, protect the credentials, and operate the scheduler.
Does KapKit store my social credentials?
No. The product direction is buyer-owned credentials in the self-hosted installation. Secrets stay in the owner's environment, password manager, or protected PostKit connection flow.
Can an AI assistant use PostKit?
Yes. The REST API and API keys are built so an operator or agent can create drafts, upload media, schedule posts, run publish ticks, inspect results, retry failures, and sync analytics.
What is verified now?
The local product workflow can be proved with mock provider tests, source tests, and guarded provider setup flows. Live third-party posting depends on real platform credentials, scopes, account eligibility, quota access, and platform review.
Stop renting the posting workflow
Own it.
If your business already depends on a rented social scheduler, PostKit gives you the owned alternative: one dashboard, one API, one server, and clear official-provider boundaries.