Clone it, own it, ship faster. 45+ integrated packages: auth (Auth.js v5), RBAC, multi-tenancy with RLS, job queues, blog/CMS, realtime WebSockets, per-tenant branding, shadcn/ui, and way more. Built around OttaORM - a fat model system where business logic lives in models, not controllers. Auto-migrations, CRUD APIs, and TanStack Query hooks are all generated from a single model definition. Your code, your stack, your infra.
I'm the solo founder behind Ottabase, and I want to share what drove me to build it.
Every new side project I started followed the same painful pattern: two to four weeks of wiring up auth, multi-tenancy, RBAC, queues, and an email system before writing a single line of actual product code.
The frameworks I tried either locked me into a SaaS subscription, were heavily Node/server-dependent, or required me to bolt multi-tenancy onto an architecture that wasn't designed for it. I wanted something edge-native (Cloudflare Workers), truly open-source (clone and own), and opinionated enough that the boring decisions were already made.
So I built Ottabase over the past year: A monorepo with 45+ integrated packages covering everything from auth, RBAC, and job queues to a blog engine, realtime WebSockets, per-tenant branding, and full sets of UI components and libraries.
The two ideas I'm most proud of are OttaORM's "fat model" pattern and the Brand Engine. With fat models, you define your schema once in a model class and automatically get auto-migrations, a REST CRUD API, and TanStack Query hooks. Business logic lives in one place, and multi-tenant Row-Level Security is enforced at the ORM layer - not left as something you remember to wire up correctly.
The Brand Engine does per-route dynamic theming and templating, so each tenant can feel like they have their own product without you writing a single one-off CSS override. Those two pieces together are what make Ottabase feel like a real framework rather than just a collection of disparate packages.
I'd love to hear what you think especially the last para stuff, and what packages you wish were already included. AMA!
No comment highlights available yet. Please check back later!
About Ottabase: The Solo Founders' Framework on Product Hunt
“Ship in days, not months. Cloudflare-native SaaS monorepo.”
Ottabase: The Solo Founders' Framework was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #123 on the daily leaderboard. Clone it, own it, ship faster. 45+ integrated packages: auth (Auth.js v5), RBAC, multi-tenancy with RLS, job queues, blog/CMS, realtime WebSockets, per-tenant branding, shadcn/ui, and way more. Built around OttaORM - a fat model system where business logic lives in models, not controllers. Auto-migrations, CRUD APIs, and TanStack Query hooks are all generated from a single model definition. Your code, your stack, your infra.
Ottabase: The Solo Founders' Framework was featured in Open Source (68.3k followers), Developer Tools (511k followers), Artificial Intelligence (466.2k followers) and GitHub (41.2k followers) on Product Hunt. Together, these topics include over 182.6k products, making this a competitive space to launch in.
Who hunted Ottabase: The Solo Founders' Framework?
Ottabase: The Solo Founders' Framework was hunted by thinkdj. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Ottabase: The Solo Founders' Framework stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
thinkdj
Hey Product Hunt! 👋
I'm the solo founder behind Ottabase, and I want to share what drove me to build it.
Every new side project I started followed the same painful pattern: two to four weeks of wiring up auth, multi-tenancy, RBAC, queues, and an email system before writing a single line of actual product code.
The frameworks I tried either locked me into a SaaS subscription, were heavily Node/server-dependent, or required me to bolt multi-tenancy onto an architecture that wasn't designed for it. I wanted something edge-native (Cloudflare Workers), truly open-source (clone and own), and opinionated enough that the boring decisions were already made.
So I built Ottabase over the past year: A monorepo with 45+ integrated packages covering everything from auth, RBAC, and job queues to a blog engine, realtime WebSockets, per-tenant branding, and full sets of UI components and libraries.
The two ideas I'm most proud of are OttaORM's "fat model" pattern and the Brand Engine. With fat models, you define your schema once in a model class and automatically get auto-migrations, a REST CRUD API, and TanStack Query hooks. Business logic lives in one place, and multi-tenant Row-Level Security is enforced at the ORM layer - not left as something you remember to wire up correctly.
The Brand Engine does per-route dynamic theming and templating, so each tenant can feel like they have their own product without you writing a single one-off CSS override. Those two pieces together are what make Ottabase feel like a real framework rather than just a collection of disparate packages.
I'd love to hear what you think especially the last para stuff, and what packages you wish were already included. AMA!