24fec62d7f
Forked clean from public hackathon repo (Starfire-AgentTeam, BSL 1.1) with full rebrand to Molecule AI under github.com/Molecule-AI/molecule-monorepo. Brand: Starfire → Molecule AI. Slug: starfire / agent-molecule → molecule. Env vars: STARFIRE_* → MOLECULE_*. Go module: github.com/agent-molecule/platform → github.com/Molecule-AI/molecule-monorepo/platform. Python packages: starfire_plugin → molecule_plugin, starfire_agent → molecule_agent. DB: agentmolecule → molecule. History truncated; see public repo for prior commits and contributor attribution. Verified green: go test -race ./... (platform), pytest (workspace-template 1129 + sdk 132), vitest (canvas 352), build (mcp). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.1 KiB
1.1 KiB
SaaS Upgrade Path
The open-source project has no auth. This is intentional — the project follows the n8n Community Edition model.
How It Works
When productizing as SaaS, a separate molecule-cloud repo wraps this project and adds:
| Feature | Technology |
|---|---|
| Authentication | Clerk or Auth.js |
| Multi-tenancy | Org isolation (org_id added to schema) |
| Billing | Stripe |
| Managed infrastructure | ECS + Neon + Upstash |
| White-labelled canvas | Custom branding |
Key Principle
No changes to this repo are needed. The SaaS layer is purely additive. The open-source core remains clean and self-hostable.
Schema Changes
The MVP schema intentionally omits org_id. It is added in the SaaS migration for multi-tenancy isolation. This avoids cluttering the open-source schema with fields that only matter for hosted deployments.
Related Docs
- Constraints & Rules — Design decisions that enable this
- Architecture — System overview
- Database Schema — MVP schema that
org_idextends