Starship is the voucher platform behind Rocket Incentive — a branded web portal and a production-grade REST API, both backed by inventory-first fulfillment and slick integrations with the vendors that matter. Cache hit means delivered in milliseconds. Miss means admin-gated vendor fallback. No double-spend, no ghost allocations, ever.
Serve enterprise buyers through a branded portal, or wire partners in directly over REST. Same inventory, same allocation guarantees, same audit trail.
A production-grade Next.js portal per client. Wallet, catalog, cart, orders, exports, and reports — all branded, multi-currency, and backed by the same inventory pool the API uses.
A versioned REST API for partners who want vouchers delivered as a service. Auth, idempotency, webhook callbacks, and a clean request/response model — documented and battle-tested.
/api/v1/* endpointsOpinionated coverage of the voucher lifecycle — from catalog sync to reconciled delivery — with the sharp edges already filed down.
Orders hit the cache first. Instant delivery on hit, admin-gated vendor fallback on miss. No surprise upstream calls.
Atomic ZPOPMIN from a sorted Valkey pool. Zero double-allocation under concurrent load, deterministic under contention.
ZSet sorted pool plus HSet metadata, kept in lockstep by a 108-key invalidation matrix. No drift, no orphans.
USD, EUR, GBP, CAD, AUD, SGD, NZD, PHP, and more. Live FX rates, per-client currency locking, per-product denominations.
Every vendor fallback, price change, and exception passes through an admin gate with a full audit trail. No silent auto-spend.
Delivery confirmations, partial fulfillments, retries, and reconciliation drifts — all as signed, replay-safe webhook events.
Background jobs match every allocation to vendor-side records. Drifts are auto-flagged for operator review, not auto-trusted.
Real-time ops console: inventory depth by vendor, order queues, pending retries, reconciliation health, pump metrics.
Production integrations with the suppliers your customers actually ask for — HMAC signing, catalog sync, webhook callbacks, idempotency, all battle-tested.
Four stages turn a vendor catalog into a fulfilled order — with cache-backed instant delivery on the happy path and admin-gated fallback when it isn't.
Vendors publish catalog + denominations. Starship normalizes currencies, countries, and SKUs.
Imported vouchers land in the dual-layer Valkey cache. ZSet sorted by priority & expiry, HSet for metadata.
Web or API order → cache lookup. Hit: delivered in under 1 ms. Miss: admin-gated vendor fallback.
Every allocation matched to vendor records. Drifts flagged, never auto-resolved.
A layered architecture you can reason about at 2am — Go/Fiber API, two Next.js frontends, a Valkey cache that does one job well, and PostgreSQL as the record of truth.
The cache isn't a performance afterthought — it's the allocation engine. Two complementary structures, one invariant: what the pool sees is what the metadata sees.
Each vendor's available vouchers live in a Valkey Sorted Set, scored by priority and expiry. Allocation is a single atomic ZPOPMIN — guaranteed-unique selection under concurrent load.
Every voucher has a companion Hash holding denomination, vendor, expiry, and status. A 108-key invalidation matrix keeps pool and metadata in perfect lockstep — no orphan entries, no ghost allocations.
Running live with real clients, real vendors, and real money moving through it.
What enterprise buyers and API partners actually ask before signing.
PENDING status. Vendor fallback is an explicit admin action with a full audit trail. This is a deliberate design choice: silent auto-spend on a partner API is how you end up with reconciliation nightmares.Tell us about your volumes, vendors, and timelines. We'll scope it honestly and show you the parts that are already done.
Request a Demo