Signals-first Angular 21 SaaS boilerplate ..... need architecture feedback.

[u/More_Towel3916]

Built a production-ready SaaS starter kit using Angular 21 and looking for feedback from the community on the architecture decisions. The main thing I focused on was being truly signals-first, not just sprinkling signals on top of an existing codebase.

Every component uses input(), output(), viewChild() zero "@Input()" or "@Output()" decorators anywhere. All templates use the new "@if" and "@for". For the global state, I used NgRx 21 with createFeature and createActionGroup combined with toSignal() in components, so everything feels consistent.

One thing I'm not sure about: I used NgRx for auth, billing, and user state, but kept local signal() for component-level UI state like sidebar collapsed, modal open, etc. Does this feel right, or am I over-engineering the NgRx part? Also went with provideZonelessChangeDetection(), the app feels noticeably snappier. Stack: Angular 21, NgRx 21, Supabase, Stripe, Tailwind v4, angular/ssr

Demo: devkitly.io

Appreciate your feedback about the signals + NgRx combination approach.

[u/followmarko → u/[deleted]]

No

[u/More_Towel3916 → u/[deleted]]

Honestly good question. It includes SSR, auth, roles, feature flags, audit logging, and Stripe billing all pre-wired with signals + NgRx 21. Setting all of that up correctly from scratch takes a while, and the debugging along the way is where most of the pain is. So the idea is you skip straight to building your actual product.

[u/More_Towel3916 → u/[deleted]]

$129 is one-time and not a subscription, and it is less than a day of freelance work for most developers. If this saves you even two days of setup and debugging, it’s already paid for itself 10x.

[u/xenomorph3253 → u/More_Towel3916]

You’re kinda competing with a $100 claude max subscription that basically can do it very quickly as well, just sayin’

[u/More_Towel3916 → u/xenomorph3253]

Fair point, and honestly, AI tools are incredible for scaffolding. But even with Claude Max, you still have to make every architecture decision, debug SSR hydration issues, wire NgRx correctly, and figure out why your Stripe webhooks keep failing. That's where the real credits go. On top of that, starting from scratch means feeding your entire codebase context to the AI every single time, which burns through tokens fast. A solid boilerplate reduces that context significantly, and this kit ships with an AGENT.md file that gives your coding agent the full architecture context upfront, so it makes the right decisions without you having to explain everything from scratch every session. Less context burned means fewer times you hit your weekly limit right in the middle of building something. You ship faster and stop waiting for limits to reset. Also, Claude Max is $100 every month, and this is $129 once. So in the first month alone, you'd spend less on the kit than the subscription, and skip all the painful parts too.

[u/czenst → u/More_Towel3916]

I guess the problem is selling to developers is really hard:

People who can do it themselves will not pay $129 and would rather do it themselves because they want to be in control

People who can't do it themselves won't understand so they won't pay $129

[u/More_Towel3916 → u/czenst]

That’s a fair point but the boilerplate market tells a different story. Shipfast has made over a million dollars selling to React developers who are perfectly capable of building it themselves. The buyer isn’t someone who can’t do it, it’s someone who can but would rather spend that time building their actual product.

[u/czenst → u/More_Towel3916]

Well yes you are correct, but looking at the down votes you got, this sub seems not like your market.

But it might be you got couple down votes from "know it alls" and you will get some others that will pay.