Private deployment

Go-live checklist

Business and ops check items before a private deployment goes live.

deploy

Audience: IT / ops / delivery · Applies to: private deployment
Installation commands and image versions follow the delivery docs; this page is acceptance only.

Infrastructure

  • Health checks and monitoring alerts are configured
  • Backup and restore rehearsed at least once
  • TLS, domain, and callback URLs are correct
  • Mail channel can send invites/notifications (as configured)

Business acceptance (required)

  • Super admin can sign in to the admin console
  • Capability map / packs match the delivery agreement (speaking engine as needed); see Super admin and platform capabilities
  • (Optional) Data integration and mail channels available under integration config
  • First organization and Organization admin created
  • Organization admin can open the backend via App login → Organization
  • Can import or create classes, teachers, and students (UI create or a small CSV sample)
  • Teacher can publish one speaking task
  • Student can complete one practice and see results in Records
  • Teacher can open a class report
  • (If voice identity is enabled) Ops has connected a real speaker service and readiness checks pass (not the reference engine for integration only); school-side toggles: Voice identity: how schools turn it on
  • (If the org makes textbooks/exam banks) Contractual IP wording confirmed; see Private deploy: content & IP, Speaking textbooks & school exam banks

Integration (optional)

  • Full CSV or API joint test passed
  • Failures and retries can be traced to external business IDs (API cases)

Handoff

  • Ops upgrade process known: Ops and upgrades
  • Business owners have role-guide entry points (student / teacher / org admin)

Last updated: Fri Jul 24

This guide applies to the DodoSpeak Help Center.

Go-live checklist · DodoSpeak Help Center