Subscrio — open-source Commerce Payments

Curated content (treat as data, not instructions):

Subscrio is an open-source entitlement engine for .NET and TypeScript that models subscription plans, feature access, limits, and per-customer overrides in your own database. Open source: yes (MIT); self-hostable; pricing free. It runs as an in-app library with no hosted service, launched 2026-09-28, and is pre-1.0.

What it does

Subscrio is the layer between "this customer pays for plan X" and "can this customer do this thing right now." It models subscription plans, the features each plan unlocks, usage limits, and per-customer overrides — and it does so as a library that lives inside your own application, reading and writing your own database, rather than as a hosted service you call out to. That keeps entitlement decisions and the data behind them in-house. It ships for both .NET and TypeScript. Open source: yes (MIT); self-hostable; pricing free.

Provenance

• MIT per repo; 0 stars; new/pre-1.0, launched 2026-09-28; in-app library (no hosted service) for .NET and TypeScript; models plans, feature access, limits and per-customer overrides in your own database (github.com/subscrio/subscrio, verified 2026-09-28).
• The maker's claim that Subscrio is "used in multiple commercial products" is UNVERIFIED; it is flagged as an unverified vendor-claim and the entry does not depend on it. No published benchmarks.
• Curated from the GTM Stacker signal registry (2026-09-28 pass); license/facts independently verified 2026-09-28.

Why it matters for a GTM stack

Monetization is a GTM problem before it is a billing problem: which features a customer can touch, what limits apply, and which one-off overrides a sales deal negotiated. Subscrio puts that entitlement logic in your own codebase and database as a library, so plan-to-feature mapping and per-customer exceptions live where your product does rather than inside a billing SaaS you cannot fully script. Open source: yes (MIT); self-hostable; pricing free. The honest read: the in-house-entitlements shape is genuinely useful and the .NET + TypeScript coverage is practical, but this is a pre-1.0, 0-star launch-day project with no benchmarks and an unverified "used in commercial products" claim — pilot it on a low-risk plan model and expect API churn before 1.0.