Support
by @ops Support Impersonation ("Login as Customer") Tool Backend
Secure, time-limited support impersonation with a full audit trail of who impersonated whom and when — distinct from the Support Ticketing recipe: that's the ticket/thread system, this is the specific, sensitive capability of seeing the product as a customer sees it.
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 support-impersonation-tool --remote $ stacktora sync # generate the files
What you get
More from the Vault
Customer Support Ticketing Backend
Tickets, threaded replies, and status/assignment state in Postgres, with Redis for the stuff that needs to be fast (unread counts, live status). The backend behind a support inbox, not a full helpdesk UI.
.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.