Skip to content

Phase 10 — Launch

Goal: open Router.Africa to the public with open sign-up, onboard the friendly customers, and watch the first week closely.

Milestone M4: v1.0.0 is live in production, sign-up is open, and the first customers are making paid requests.

ID Task Who Needs Status
P10.01 Launch configuration You P9.14 todo
P10.02 Release v1.0.0 You + agent P10.01 todo
P10.03 Open sign-up and onboard customers You P10.02 todo
P10.04 First-week review You + agent P10.03 todo

Who: You · Needs: P9.14

In the production admin app, set:

  • Markup values (screen 43).
  • Hold parameters per model: max_tokens ceiling and default, and input allowance (screen 45).
  • Minimum hold and rate significant figures (rate_sig_figs, default 3) per currency (screen 44).
  • Top-up fees per vendor and currency (screen 51).
  • Currencies: enable every Niobi market (Launch scope (markets)).
  • Models: enable the launch models and set the onboarding defaults (screen 45).

Then run the rates job.

  • Spec: ../product/pricing-model.md Open Items; decisions log, Launch scope (markets), v1 model list
  • Done when: every enabled model has a published rate in every enabled currency, and a test top-up quote shows the right fee.

Who: You + agent · Needs: P10.01

  1. Cut release/1.0 from main and tag v1.0.0.
  2. Run Deploy to production.
  3. Confirm the smoke check passes.
  4. Watch the 15-minute window: 5xx rate, settle failures, queue lag.
  5. Confirm the canary and the status page are green.
  • Spec: ../architecture/cicd.md sections 6–8
  • Done when: the deploy and the watch window are clean, with the rollback path (the previous tag) confirmed available.

P10.03 — Open sign-up and onboard customers

Section titled “P10.03 — Open sign-up and onboard customers”

Who: You · Needs: P10.02

  • Point the marketing site’s sign-up links at app.router.africa.

  • Publish the docs and status page links.

  • Onboard the friendly customers, and set up a support channel.

  • Keep an eye on new sign-ups, the edge rate-limit hits and the low-balance emails.

  • Spec: ../product/website-copy.md; decisions log, Launch shape

  • Done when: the first customers have topped up and are making requests in production.

Who: You + agent · Needs: P10.03

A week after launch, review:

  • alert thresholds and noise
  • the leaked-key detection thresholds (api-key-security.md 7.2)
  • costs against estimates (droplet, R2, Datadog, Workers, GitHub minutes)
  • the reconciliation results
  • margin by model and currency
  • what customers asked for

Record the changes. Move requested features to the build inventory’s Later list or the future-optimizations register.