PROJECTS
brightbean.xyzBrightBean Studio
A self-hostable social publishing workspace with a calendar, platform-specific drafts and approval steps.
On this page
Social scheduling and approvals
Use one upcoming post to check the path from draft to approval and see whether your publishing platforms and credentials fit the setup.
What it’s useful for
BrightBean Studio puts planning, composition and approval around the same social post. It offers a self-hosted route for people who want to operate their publishing system, alongside the publisher’s hosted service. Its platform matrix is more useful than a single network-count headline: a network may support publishing without every inbox or analytics feature.
Inside the product
- Plan posts with a visual calendar, recurring slots and named queues.
- Write per-platform captions and media variants in the same composer.
- Use workspace roles, internal/client approvals and documented first-party publishing integrations.
Good to know
- Self-hosting requires application operations and your own platform developer credentials; some networks require app review.
- Publishing, comments, direct messages and analytics coverage differ by network; use the repository matrix.
- No connected-account publishing, approval delivery or historical analytics migration was tested here.
The maker’s build notes
In the original Show HN discussion, the maker describes using Claude Code for planning and the first backend/UI pass, then Codex to challenge implementations and find problems. This is a maker-reported development account, separate from the optional AI features inside the product.
A few more details
Does self-hosting remove the platform setup?
No. The repository documents platform developer credentials and network-specific approval requirements. Running the application does not grant publishing access to your social accounts.
Sources & maker notes
Build details come from the maker’s linked account. vibeforthat has not independently audited the code or tested every product function.