Case Study · Deployed Product
Social Autopilot
One post, multiple platforms. Social Autopilot is a multi-tenant publishing product built around a single composer, multiple accounts per platform, scheduling and recurring posts, a content calendar, media library, drafts, CSV import and team workspaces. It is deployed, but provider publishing is not yet verified end to end across every network.
The problem
Anyone who posts to more than one network repeats the same work: open each app, re-upload the same video, paste the same caption, and try to remember to post at the right time. Existing schedulers are expensive, lock you into their platform, and rarely support multiple accounts on the same network — which agencies and creators actually need.
The approach
I built a focused, self-hostable product around one clear workflow, then made the unglamorous parts solid enough to trust:
- Write once, publish everywhere — one composer, one caption, per-network previews and caption limits.
- Multiple accounts per platform — connect several accounts on the same network and choose exactly which one each post targets.
- Scheduling & recurring posts — publish now, schedule for later, or repeat daily/weekly; each occurrence is queued automatically.
- Reliability — every platform publishes independently and is claimed atomically, so one failure never blocks the rest and nothing double-posts.
- Content calendar & media library — plan the week and reuse media you already uploaded.
- Drafts, templates & CSV import — save drafts (with local autosave), reuse captions, and bulk-create posts from a spreadsheet.
- Team workspaces — invite teammates who share the owner's accounts and posts without sharing passwords.
How it’s built
A FastAPI service renders the app and exposes a JSON API; PostgreSQL (Supabase) stores users, posts, connections and publishing history; OAuth tokens are encrypted at rest. A scheduler and a database-backed heartbeat both drive the same publishing engine, so jobs survive restarts and run correctly with multiple instances. Object storage holds media, and the whole thing deploys to Vercel.
PostgreSQL & object storage sit behind FastAPI; OAuth tokens are encrypted.
Trust & operations
Because it touches people's social accounts, security and transparency mattered: encrypted tokens, hashed passwords, CSRF protection, two-factor authentication, a session manager, a public status page and daily database backups. The public status page below reports service health in real time.
Documentation & onboarding
A built-in help center and an SEO-ready landing page make the product usable without a manual, and the dashboard guides new users through setup with a progress checklist.
Outcome
- Production deployment is available and the application serves its web experience.
- 412 automated tests are documented as passing in the project README.
- Seven provider integrations are represented in the product; real publishing remains partially configured and must be verified provider by provider.
- TikTok sandbox publishing is not yet verified, and production publishing is pending TikTok Content Posting API approval.
What I’d do next
Complete provider-by-provider end-to-end publishing verification, finish external platform approvals (including TikTok production access), connect and verify live payments, and continue improving analytics and operations.