OPEN SOURCE · SELF-HOSTED · APPROVAL-FIRST
Your content operation.
One visible system.
Discover relevant signals, shape on-brand drafts, review with confidence, publish deliberately and retain what you learn — inside your own deployment.
01 / THE OPERATING LOOP
Prompts create text.
Systems create continuity.
Social Machine keeps the source, editorial context, review decision and result connected from one stage to the next.
Discover
Bring trends and trusted sources into one workspace.
Curate
Rank relevance and remove duplicate ideas.
Create
Shape drafts with the voice and rules of the workspace.
Review
Make quality checks and human decisions visible.
Publish
Enable a channel only after the process is ready.
Learn
Feed evaluation and performance into the next run.
02 / PRODUCT TOUR
One workspace.
Clear stages.
Illustrative counters demonstrate workflow state transitions, not customer results.
03 / CONTROL IS THE PRODUCT
Automation
is earned.
Start with human approval. Add providers, publishing, video and schedules only after the editorial and technical path is reviewed.
- Workspace isolationBrand, accounts and settings belong to their owner.
- Features off by defaultOptional integrations do nothing until configured.
- Traceable decisionsSources, quality checks and review states stay connected.
04 / YOUR INFRASTRUCTURE
The foundation is included.
The operation stays yours.
Deploy the Next.js dashboard against a new Supabase project. Bring only the providers and channels your team chooses.
+ SUPABASE
05 / SAFE START
Clone first.
Connect carefully.
Start with a new Supabase project, new secrets and no active publishing. Follow the onboarding before enabling integrations.
Read the complete quick startgit clone https://github.com/luisroquette/social-machine-for-all.git
cd social-machine-for-all
cp .env.example .env.local
npm ci
npm run audit:public-release
npm run devVISIBLE DECISIONS · CONTROLLED PUBLISHING