FIELD MANUAL — OWN YOUR FLEET
One idea in.Published video out.
Socheli is the open-source social media manager that creates, publishes, and grows. It scripts, voices, renders, and posts on its own. Your devices do the work. Your disk keeps the data.
~130 tools, one registry 5 surfaces: CLI / API / MCP / SDK / copilot MIT-licensed packages renders on your device posts from your phone flat JSON, no database
0 — A RUN, REPRINTED
$ content new --channel mychannel trends → idea ...... 46s "How Sri Lanka handed China a port for 99 years" hook ............... 18s "Colombo took the loan. Beijing took the port." script ............. 51s storyboard ......... 1m06s 8 scenes · 28s cut fact-check ......... flagged a misattributed loan figure → revised QA ................. passed 8/10 music · b-roll ..... 2m32s 119 beats matched · 5 sfx cues render ............. 1m44s 1080×1920 · Remotion → gate: WAITING FOR HUMAN → approve to publish
1.0 — IDEA
It starts as one sentence.
You give Socheli an idea: a topic, a take, a question. That's the whole input. The channel's Brand Genome of learned hooks, topics, and formats shapes everything that follows. Or you give it nothing, and it reads the trend scan instead.
2.0 — SCRIPT
The engine writes like the channel.
The brain drafts hooks and scenes against the genome, then a fact-check pass challenges every claim. Fig. 1 shows it catching one. Every field is readable, every shape is a zod schema. You can open the file.
3.0 — STORYBOARD
Frame-accurate before a single pixel renders.
Scenes, timings, emphasis, b-roll queries: locked in JSON, validated at the boundary, rendered exactly as written.



4.0 — RENDER, ON YOUR DEVICE
Your hardware does the work.
Remotion compositions render locally. Your GPU, your filesystem, your media. Nothing uploads to a render farm, because there isn't one.2
▶ load the real output
Fig. 2b — actual output, unretouched. render 1m44s · 1080×1920 · Remotion
5.0 — PUBLISH, FROM YOUR DEVICES
Nothing posts without your gate.
The mission loop runs until you stop it. Publishing drives your own phone, on your own accounts, over your own IP. The gate is yours.
THE TRUST BOUNDARY
- nothing publishes without your gate
- the mission loop runs until you stop it
- your machines do the work
6.0 — SPECIFICATION
Create. Publish. Grow.
Socheli is the open-source social media manager. One engine runs the whole loop, from a one-sentence idea to a posted video to the lesson it leaves behind in the brand's genome.
Create
- one idea becomes script, voice, music, and b-roll in a single run
- storyboard-first Remotion renders, 9:16 vertical and 16:9 long-form1
- fact-check and QA passes challenge every claim before render
- mood system, native motion graphics, and generated thumbnails
- a Brand Genome per channel: learned hooks, topics, formats, voice
Publish
- posts from your own devices, on your own accounts, over your own IP
- a human gate before anything goes live, unless you open it on purpose
- a scheduler that learns the posting times your audience actually keeps
- Instagram, YouTube, and TikTok, with covers and per-platform packaging
- comment-to-DM triggers and an AI responder for DMs and comments
Grow
- a verified research harness: sweep, cross-check, cite, then plan
- algorithm playbooks per platform fill a dated content calendar
- missions: the always-on manager loop that works while you don't
- per-post insights feed engagement lessons back into the genome
- genome evolution stays gated: you approve what the brand learns
every capability, all five surfaces: CLI · HTTP API · MCP · SDK · copilot — ~130 tools, one registry · license: MIT packages2 · github.com/Socheli
Socheli does not
- render in our cloud
- hold your tokens
- post without your gate
- phone home
- require a database
- run analytics on this page3
7.0 — QUESTIONS
Does it need my API keys?
Yes, your own. Model and voice providers are called with keys you supply, stored in a local .env on your machine. There is no Socheli server in the loop to send them to.
Why my own devices?
Rendering is compute you already own, and publishing from your own phone on your own IP means your accounts behave like accounts, not like an API farm. Ownership is the architecture, not a feature flag.
What does Meta App Review see?
Socheli requests Instagram permissions through Meta's standard OAuth, per workspace. Tokens are stored as flat JSON on the user's own device and are deletable by the user at any time. See Privacy and Data Deletion.
What happens when I stop it?
The mission loop halts at the next tick. Nothing renders, nothing posts, nothing phones home. Your data is flat JSON on your disk. Delete the folder and it's gone.
What's the license?
MIT. The CLI, SDK, MCP, and API packages are public on GitHub and npm today; the engine core opens with the public launch. The terms are written in plain language at /terms.
- 1 — timings measured on the maintainer’s own laptop; unedited log at Fig. 1, run concept_20260611090005 · commit 248dfa5
- 2 — MIT on the published packages (@socheli/cli, sdk, mcp, api); the engine core repository opens with the public launch
- 3 — verify in your DevTools network tab — this claim is checkable