Backend
by @ops Node + Postgres + Redis: Franchise & Multi-location Operations Baseline
Per-location performance, compliance checklists, and franchisee records rolled up to an owner view — a starting shape for any multi-location operator, not a single-site business.
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install franchise-multilocation-ops --remote $ stacktora sync # generate the files
What you get
More from the Vault
.NET + Postgres + Redis: Field Sales CRM & Visit Tracking
Sales rep visit logging, territory assignment, and account history — a genuinely common field-sales vertical not yet in the catalog, distinct from the Field Service Technician recipe (that's repair/installation work, not sales visits).
.NET + Postgres + Redis: Fintech-oriented Baseline
A security-conscious starting point for financial and payments-adjacent backends: .NET API, Postgres for ledger/transaction records, and Redis for session and rate-limit state. This is a starting baseline only, not a certified or verified PCI-DSS/regulatory-compliant stack — your own security and compliance review is still required before handling real financial data.
.NET + Postgres + Redis: Insurance Policy Quoting Engine
Rate calculation and quote generation before a policy exists — distinct from Insurance Claims Processing: that handles claims after something happens, this is underwriting math and quote state before a customer ever buys.
.NET + Postgres + Redis: Retail Point-of-Sale (POS) Backend
In-person transaction handling, cash drawer reconciliation, and receipt records — distinct from e-commerce/inventory recipes built around online orders: this is the in-store, register-shaped side of retail.