nextanative

nextanative is a pop-punk idol group in Jakarta. Their core product is the cheki, a polaroid photo session with one member of the band, and it used to be sold through WhatsApp, Google Forms and spreadsheets. This is the platform that replaced that: a public site, a members app, a staff console and one API, built as a Turborepo where the business rules live in Postgres rather than in the clients. One fan identity carries every order, card, badge, stamp and voucher, which is what makes a loyalty economy possible at all.

Cheki demand is a queue of people trying to buy the same few slots at once. Two fans claim the last slot in the same second and the quota is sold twice. Someone holds a slot and never pays, so inventory stays frozen while real buyers are turned away. Member presales are a form link that leaks in minutes. The split between idol, management and photographer is reconciled by hand after every event. None of that is a screen problem. The hard part is keeping a slot sold exactly once, an early access window closed to the wrong tier, and a payout reproducible months later.

• Designed the schema across 84 migrations: events, quotas, orders, collectible cards, badges, ledgers, vouchers and support tickets.
• Wrote the API as 56 Hono route modules on Cloudflare Workers, with JWKS token verification and role middleware.
• Built all three front ends: the Next.js public site, the Vite fan app and the Vite admin console.
• Wrote the Postgres functions that hold the risky rules: booking expiry, card claims, stamp redemption and badge eligibility.
• Set up deployment on Workers and Pages with staging and production environments, secrets and scheduled jobs.

1. 01

   Cheki ticketing

   cheki_events · cheki_event_members

   Pre-order and door sales are two channels on one event, each with its own quota, bundle price and form. Quotas can be capped per member or pooled, and a form can gain a field without a migration because the answers land in JSONB.

2. 02

   The fifteen minute hold

   pg_cron, every 60 seconds

   A fan holds a slot while they transfer the money. A database function expires the hold, returns the quota and flips the state in one statement, so a slow transfer cannot lock inventory for the rest of the day.

3. 03

   Early access enforced in Postgres

   RLS policies on cheki_submissions

   Member presales are timing windows the database evaluates against the fan's membership tier. A leaked link, an edited request body or a hand written curl call meets the same policy, because there is no check in the client to remove.

4. 04

   Door sales on a tablet

   Cashier · check-in · shift recap

   The on-the-spot flow is built for one hand and a queue of two hundred: carts across several members, bundle pricing applied automatically, a recap at the end of each shift, and a batch code the crew writes on the back of the physical polaroid.

5. 05

   Collectibles and achievements

   card_claims · achievements.rules_config

   A purchase can claim a collectible card into a digital binder and earn one of 40 badges. Each badge is a row with a rule, a hint, a progress style and two visual states, so a new achievement is an insert rather than a deploy.

6. 06

   A currency that cannot pay twice

   volt_ledgers · stamp_ledgers

   VOLT and loyalty stamps are append only ledgers with a unique key on user, reference and type. Balance is a sum, a replayed reward becomes a constraint violation, and every grant can be traced back to what caused it.

• 01

  No automated tests yet

  Correctness rests on database constraints, type checks and manual QA at live events. SQL tests for booking expiry, stamp redemption and card claims come first, then tests around bundle pricing and date handling.

• 02

  Two shared packages are declared, not extracted

  The shared UI still lives twice, once in the fan app and once in the admin app. The package exists and the build already resolves it; the move itself has not happened.

• 03

  The gacha terminal is built and switched off

  It ships behind a flag that defaults to off. Drop rates and currency sinks need tuning before it can open.

• 04

  The admin console is Indonesian only

  Operations staff are internal, so localising it would add maintenance without a reader.

• 05

  These screenshots are schematics

  The repository is private and the artwork belongs to the band. Each frame on this page is a placeholder that can be swapped for a real capture once permission is in writing.

At a live event the platform covers the whole loop: registration, pre-order, payment approval, door sales, card claims, badges, loyalty vouchers and the payout report. The numbers that would make the strongest case (orders processed, members onboarded, hours of reconciliation removed) belong to the band, so they are not published here. What is public is the shape of the system and the rules it enforces.