Skip to main content

Production Deployment

This guide is the go-live checklist before real customers and employees rely on Qefro. Qefro cloud is already hosted — “deployment” means production readiness of your tenant configuration.

Outcome​

  • Support and/or Employee workspaces cite-tested
  • Channels bound correctly (widget / WhatsApp / portal)
  • RBAC least-privilege
  • Tools (if any) hardened
  • Billing and monitoring understood
  • Rollback / disable plan documented

Architecture reminder​

Platform: Deployment.

Checklist​

Knowledge​

  • Customer vs employee corpora are in separate workspaces
  • Top 20 questions cite correctly; unknowns refuse
  • Stale docs removed or reindexed

Customer AI​

Employee AI​

Business Actions​

  • No write tools on public workspaces without review
  • Secrets encrypted; rotation owner assigned
  • identify() used when APIs need end users
  • Tool logs reviewed for pilot traffic
  • Guide: Secure Business Actions

Security & compliance​

  • Security Overview reviewed with stakeholders
  • DPA / questionnaire completed if required
  • Staging org used for experiments when possible
  • Docs: Security Overview, Compliance

Billing & ops​

  • Plan limits understood (messages, docs, WhatsApp)
  • Payment method valid; webhook-driven entitlements confirmed in Billing UI
  • Owner contact + support escalation path documented

Workflow​

Production gate

  1. Freeze corpus for pilot — Cite-test top intents.
  2. Enable one channel — Website first.
  3. Add staff access — RBAC for Employee AI if in scope.
  4. Optional tools — Read-only → monitored writes.
  5. Watch one week — Analytics, feedbacks, tool logs.

Rollback​

If something goes wrong:

  1. Remove or comment out the website widget script.
  2. Disable WhatsApp in Admin Console / Meta routing.
  3. Disable Business Tools on the affected workspace.
  4. Rotate tool credentials at the vendor if abuse is suspected.

FAQ​

Do I deploy containers myself?
Not on Qefro cloud. You configure the tenant. Enterprise private deployment is a separate conversation — see Deployment.
What is a staging strategy?
Create a separate organization for experiments, or a clearly named staging workspace that is never bound to production channels.