A forkable SaaS starter with auth, private files, to-dos, a document editor, agents and skills, chat, and server-side OpenRouter settings. No marketing product coupling.
Keep these surfaces. Chat and documents call OpenRouter. There is no scheduled automations product.
Email sign-in, optional two-factor authentication, and row-level security on user data.
Private per-user files in the user-files bucket, with signed download links.
Create, complete, and delete tasks. Each row is scoped to the signed-in owner.
TipTap documents stored as JSON, with optional OpenRouter AI edits and .docx export.
Users can store an OpenRouter key server-side. The browser only sees a masked status.
Upload skill markdown and assign it to General agent or Task Management. Plain General chat does not load those skills.
Multi-turn OpenRouter chat with an agent switcher, skill context, and file attachments.
Profile, password, and MFA for users. Site title, support details, and the AI Docs model for admins.
Stand up a new project, sign in, and use the keep-set dashboard.
Point this starter at a new empty Supabase project. Do not reuse another product’s database.
Register, optionally enable MFA, then use Files, To Do, Documents, Chat, and Agents.
Set a default OpenRouter model in Admin, or add a personal key in User Settings.
Demo tiers from environment variables. This starter does not bill.
All plans include:
Use a new Supabase project. Set NEXT_PUBLIC_PRODUCTNAME to your product name.
Create an account