Beta launch checklist

Our public readiness reference — what we check before opening MidgaMKT to a new community.

Foundation

  • Production database migrated

    All Prisma migrations applied via prisma migrate deploy.

  • Counties and categories seeded

    Run npm run db:seed against production once.

  • First moderator account promoted

    UPDATE "User" SET role = 'ADMIN' for the operations lead.

  • Custom domain configured (if applicable)

  • Backups confirmed

    Daily Railway / Postgres backup retention verified.

Trust and policies

  • Trust pages reviewed

    Verification, reviews, community standards, reporting, claims.

  • Legal pages reviewed by counsel

    Privacy, terms, acceptable use, disclaimer.

  • Support email monitored

    Inbox checked at least daily during beta.

Adoption

  • Founding Member list curated

    Identify 20–50 anchor businesses to invite in the first wave.

  • Onboarding emails drafted

    One-pager describing how to create a profile and request verification.

  • First listings prepared

    Seed a few real listings so the marketplace doesn't feel empty.

Public readiness

  • Sitemap exposed at /sitemap.xml

    Confirm the route returns a valid sitemap in production.

  • robots.txt allows indexing

    /admin and /dashboard remain disallowed.

  • 404 page reviewed

    Friendly recovery links to main areas.

  • Mobile spot-check complete

    Open each top-level page on a phone and confirm no overflow or broken interactions.

Curious how things work under the hood? See how MidgaMKT works.