OneForAll

I designed and built OneForAll on my own: the web app, the background worker, the database schema, the MCP server, the landing page and the server setup.

• Nothing goes out without the user’s OK: no post is published and no message is sent unless that item was approved. AI only writes drafts.
• No made-up claims: AI drafts may only use facts stored in the app, such as the brand profile, a lead’s facts or the résumé, and checks run on every draft before it can be approved.
• It is a public app, so every table has a workspace id and every query goes through a helper that requires one. One user never sees another’s data.
• No fake data on screen: counts, scores and previews are real, or they are left out.

The app is Next.js (App Router, TypeScript) with Server Actions and no separate API server, in English and French. Better Auth handles sign-up and sign-in, and its organization plugin is the workspace. Data lives in PostgreSQL through Drizzle, with real migrations.

Long work runs in a separate Node worker on pg-boss, a queue kept in Postgres: posts at their time, lead searches, website checks, job imports and AI batches. Each workspace has a limit on running jobs, so one busy user can’t block the others.

Business rules are plain TypeScript with no Next.js imports, so the screens, the worker and the MCP server share one copy of every rule. Each social platform is one module behind one interface and exports its rules as data (text limits, media rules), so the composer warns early and the worker rarely fails late.

An MCP server lets me list, schedule, edit and cancel posts from the terminal, through the same service code and checks as the screens.

The worker must always be on, which Vercel can’t do, so OneForAll runs on one server with Docker Compose. A queue like Temporal or BullMQ would add more containers or Redis. pg-boss keeps jobs in the same Postgres database, so the server runs the web app, the worker and the database, and the nightly database backup holds the queue too. The cost is a little more load on Postgres, which is fine at this size.

• 436 unit tests in 45 files (Vitest) cover the platform rules, post checks, lead logic, the job feed, the worker queue, key encryption and workspace scoping.
• 59 Playwright tests in 13 files run the main flows (sign-in, Home, Social, Leads, Jobs, Work and Settings), each at desktop and phone size.
• Not done yet: other users can connect Facebook and Instagram only after Meta’s app review.

OneForAll is live and free: anyone can sign up, add their own AI key and use Home, Social, Leads, Jobs and Work in English or French. I use it to run outreach for my own products.

• oneforall.alabaganne.com (opens in a new tab)

The landing page is public. The code is in a private repository.