No software fee
Self-hosting is not a hosted plan tier. You pay for your own servers, database, infrastructure, and any social network developer apps you use.
RedPanda Alternative scheduleron your serversame RedPanda but free
A free alternative to paid schedulers like Buffer and Hootsuite when you deploy RedPanda on your own server — no software fee under AGPL.
AGPL-3.0-or-later
Inspect and modify the source under the licence terms. You can even run your own Scheduler as SaaS as long as you stay opensource.
เลือกเส้นทางของคุณ
Hosted cloud, self-host dockerized scheduler, or your own cloud stack
Start on the upstream hosted service with a free trial, or run RedPanda yourself. Operator paths have no software fee under AGPL.
Hosted cloud plan
You want us to run RedPanda for you.
- We run updates and security for your workspace
- Start a 7-day free trial — no credit card required
- Meta, Google, and TikTok apps are ready for cloud workspaces
Docker Compose self-host
You run RedPanda on your own server or homelab.
- Run web, API, Redis, and workers on one machine
- Build from the clone or pull API and workers from GHCR or Docker Hub
- Store uploads on the server; optional CLI profile for agent login without API keys
- You manage the server, secrets, upgrades, and backups
Cloud production stack
You deploy on Vercel, Railway, or other cloud hosts.
- Run web, API, and workers on services you control
- Same scheduler with your env vars and scaling rules
- You pay for Redis, Supabase, storage, and workers in your accounts
Built for people who run their own stack
Who self-hosts, RedPanda?
Operators
You run Docker Compose or a split stack on your cloud. You own backups, TLS, and upgrades. RedPanda has no software fee under AGPL.
Teams with data control
You need posts and tokens on infrastructure you choose. Self-host keeps scheduling in your VPC or on-prem instead of a shared SaaS tenant.
Developers
You want the same public API, SDK, MCP, and CLI as cloud. You register OAuth apps with each network and wire env vars on your API host.
เริ่มที่นี่
Checklist before you go live
ข้อกำหนด การปรับใช้ และการตรวจสอบสิทธิ์ตัวแทนเพิ่มเติม — ทำตามขั้นตอนเหล่านี้ก่อนที่คุณจะเปิดอินสแตนซ์ของคุณให้กับผู้ใช้
Docker Compose self-host guide
Run RedPanda on one server — env file, Supabase, start, stop, and updates.
Docker pre-built images
Pull published API and worker images when you want a faster install.
Production deployment (custom cloud)
Run web, API, and workers on cloud hosts you pick, such as Vercel or Railway.
CLI device-login walkthrough
Blog walkthrough for agent sign-in without storing API keys on the server.
System requirements
Check disk, ports, and Supabase before your first install.
Self-hosting docs overview
How the pieces fit together and where to start in the docs.
CLI auth and OAuth server
Let agents sign in from the command line without API keys on the server.
Social integrations
Set up each social network your team will connect in the dashboard.
RedPanda Cloud overview
How hosted plans, trials, and support differ from operator-run stacks.
Cloud billing
Subscriptions, limits, downgrades, offers, and refunds on the upstream hosted service.
เชื่อมต่อช่องสัญญาณ
Set up social networks
สร้างแอปสำหรับนักพัฒนาและ env vars สำหรับแต่ละเครือข่าย ทีมของคุณเชื่อมต่อบัญชีในแดชบอร์ดเมื่อคุณเสร็จสิ้น
Connections overview
What you set up vs what your team connects in the app.
Meta Threads
Register your Meta app and connect Threads to your instance.
Get Instagram API access and link it to RedPanda.
Facebook Page
Set up a Meta app for Facebook Page posting.
YouTube
Turn on YouTube in Google Cloud and connect it.
TikTok
Register a TikTok developer app and add your callback URL.
Create a LinkedIn app and connect personal profiles.
LinkedIn Page
Set up posting to a LinkedIn Company Page.
X (Twitter)
Register an X developer app and add your callback URLs.
Dev.to
No app needed — users add their own API key in the dashboard.
Bluesky
No operator app — users connect with an app password in the dashboard.
แก้ไขเพิ่มเติม
Tune each layer of your stack
สำหรับผู้ดูแลที่ต้องการก้าวไปไกลกว่าการเริ่มต้นอย่างรวดเร็ว ให้เปิดคำแนะนำสำหรับแบ็กเอนด์ เว็บ ผู้ปฏิบัติงาน หรือส่วน CLI ที่คุณกำลังเปลี่ยนแปลง
Backend configuration
Env files, Supabase, Redis, and service keys for the API.
Supabase
Create a project, copy API keys, and match dashboard settings.
Database and migrations
Run RedPanda migrations before the first user signs up.
Redis cache
Point the API at Redis for cache and job queues.
Docker (local services)
Run Redis locally or follow the self-host Compose stack.
Upload storage (R2 or local)
Store media on disk or in Cloudflare R2 for publishing.
Google sign-in
Wire Google OAuth for dashboard login on your domain.
Email (Resend or local)
Send sign-up and notification email from your instance.
Rate limiting
Tune auth, API, and upload limits for your deployment.
Sentry
Send API errors to Sentry when you enable monitoring.
Stripe billing
Optional — enable subscriptions when you bill workspaces.
Web configuration
Vite env files and defaults for the dashboard origin.
Vite (SvelteKit)
Set VITE_* vars, HTTPS dev, and API proxy rules.
SEO and marketing defaults
Meta tags and social links for your public domain.
Config defaults
Company name, navigation, and fallback site copy.
PWA metadata
App name and icons in web-config.json.
AI crawlers and robots.txt
Let search and AI crawlers read your public pages.
Worker configuration
BullMQ workers, Redis, and the admin queue dashboard.
Workers with Docker
Start Redis and worker scripts on your machine.
Redis and queues
Share REDIS_* settings between API and workers.
Railway (workers)
Deploy always-on workers on Railway.
CLI auth server
Env vars for openquok auth:login on your network.
Auth server architecture
How device login flows between CLI, browser, and API.
Neon Postgres
Host auth-server state in Neon when you split services.
Scaling and Postgres
Run more than one auth server against pooled Postgres.
คำถามเกี่ยวกับการติดตั้งเอง
คำถามเกี่ยวกับการติดตั้ง RedPanda เอง
Common questions about cost, what you run, pre-built images, hosted vs self-host, social apps, agent login, and public servers.
Docker Compose path runs the whole app on one local server you control. Production deployment path spreads the same parts across cloud services you choose — for example the website on Vercel and background jobs on Railway. You use your own Supabase project in both cases. Neither path is the hosted plan on the upstream hosted service. Start with the Docker Compose guide or production deployment guide.
Yes. We publish ready-made images for the API and background workers. You can download them instead of building those parts yourself. You usually still build the website when your Supabase keys or public URL differ from our defaults. See Docker pre-built images and the Docker Compose guide.
RedPanda charges no software fee when you run it yourself. You still pay for servers, Supabase, bandwidth, and any social apps you register. RedPanda Cloud uses paid plans on Pricing — see the billing guide. Compare paths on Self-host RedPanda.
Docker Compose runs the website, API, queue, and workers on one machine. You can build from the repo or use pre-built images for the API and workers. A split cloud stack uses the same roles on separate services — see production deployment and worker configuration. You bring Supabase in both cases. Optional CLI setup lets agents sign in without API keys on the server. Start with system requirements.
Yes. You get the same calendar, kanban, composer, agents, Public API, and MCP tools. Plan limits on the upstream hosted service apply only to the hosted cloud product. When you self-host, you skip hosted billing and use your own social developer apps. Compare paths on Self-host RedPanda.
On self-host, yes — for networks that use OAuth sign-in. Set up only the channels your team will use, then restart the API. Dev.to and Bluesky use credentials each user pastes in the dashboard; you do not register a developer app for them. See social integration guides and Docker Compose.
Yes. Turn on the optional CLI profile in Docker Compose. Register one OAuth app for device login, then run openquok auth:login from the agent machine. See agent configuration, OAuth server admin, or the device-login walkthrough.
The default setup suits your own computer or a private network. Before you open it on the public internet, use HTTPS, limit which ports are reachable, and follow the security notes in the Docker Compose guide.
Yes. RedPanda is a free alternative social media scheduler — open source on GitHub with no software fee when you operate it yourself. Pick your path: hosted cloud plan, Docker Compose self-host, or production deployment on your own cloud. RedPanda Cloud uses Stripe billing; operator paths do not. For CLI device login without API keys on the agent host, see the CLI device-login walkthrough.
Yes. RedPanda offers one 7-day free trial per payment customer so you can run social media accounts on auto-pilot before you subscribe the plan. Create an account and start today — no credit card required. Canceling and resubscribing, or creating another workspace, does not grant a second trial. Plan limits are on Pricing and in the billing limits guide; trial rules are in the Cloud trial guide.
Workspace owners open Billing from the account menu. The billing guide covers subscriptions, limits, downgrades, promotion codes, and refunds. Compare hosted RedPanda with self-host in RedPanda Cloud.
RedPanda Cloud เทียบกับโฮสต์เอง
แผนการโฮสต์ การทดลอง และการเรียกเก็บเงินแตกต่างจากการรัน Docker Compose หรือสแต็กการผลิตของคุณเองอย่างไร
กำลังเลือกแผนคลาวด์ที่โฮสต์อยู่หรือไม่
การทดลองใช้งาน การชำระเงินแบบ Stripe ขีดจำกัดของแผน และการคืนเงินได้รับการบันทึกไว้สำหรับ RedPanda Cloud — แยกจาก Docker Compose ที่ดำเนินการโดยโอเปอเรเตอร์และสแต็กการผลิต
ขี้เกียจและไม่อยากใช้งานเซิร์ฟเวอร์ใช่ไหม?
Start a hosted workspace on the upstream hosted service. We run updates, edge TLS, and cloud OAuth apps so your team can connect channels and schedule in minutes.