Deployment
For most customers, deployment means configuring your tenant on Qefro cloud — not operating vector databases or LLM gateways yourself.
Short definition (citation-ready)
Qefro cloud hosts the Admin Console, API, widget CDN, and Internal Portal. Customers deploy by configuring workspaces, channels, and RBAC; Enterprise private deployment is a separate packaging discussion.
Production hosts
| Component | Host |
|---|---|
| Marketing | https://qefro.com |
| Admin Console | https://app.qefro.com |
| API | https://api.qefro.com |
| Widget CDN | https://cdn.qefro.com/widget.js |
| Internal Portal | your-company.qefro.com or custom domain |
| Docs | https://docs.qefro.com |
What you configure vs what Qefro runs
| You configure | Qefro operates |
|---|---|
| Workspaces + knowledge | RAG infrastructure |
| Business Tools + secrets | Tool egress + encryption |
| Widget / WhatsApp binding | Channel runtimes |
| Teams / RBAC | Auth service |
| Branding / domains | Portal edge / TLS |
Go-live checklist: Production Deployment.
Workflow
Cloud launch path
- Create org — app.qefro.com signup.
- Ship Support workspace — Knowledge + widget.
- Optional Employee AI — Portal + Teams.
- Optional tools — Read-only first.
- Monitor — Analytics + tool logs.
Enterprise / private options
If you need VPC-style or private packaging, contact Sales. Controls and tenancy concepts still apply; only the hosting boundary changes. See Compliance.
FAQ
Do I run Docker on my laptop for production?
No for Qefro cloud. Local Docker stacks may exist for Qefro engineering; customers use the hosted consoles.
Where is data hosted?
Confirm current regions and subprocessors with Sales — infrastructure details can change.