Glozr docs
/

Reseller hub

Welcome, reseller

You operate the Glozr platform. This track covers everything that lives under the workspace UI: installing the codebase, wiring Stripe at the platform level, running the super-admin console, scaling the infra, deploying upgrades, and reading the architecture so you can support your workspace owners.

Need product docs? Anything end-users do — build agents, embed the widget, manage their billing — lives in the Users track. Switch with the toggle in the header.

What you need to get started

Glozr is a self-hosted Laravel app. To go live you'll need:

  • A VPS or dedicated server with SSH access (root or sudo). About $10–15/month is enough for your first hundreds of clients — Infomaniak VPS Cloud, Hetzner CX22, DigitalOcean droplet, OVH VPS, any provider you prefer.
  • A domain you own (we wire it to your hosting during install).
  • Stripe and/or PayPal keys to collect payments (configured in the admin once you're in).
  • An OpenAI or Cloudflare Workers AI key for the AI engine (pay-per-usage, ~$0.005–$0.02 per conversation).

You don't need DevOps or Composer skills — we install everything for you within 24h after you share your hosting access. Shared hosting (cPanel shared, Plesk mutualisé, classic web hosting) is not supported because Glozr's live chat engine needs a long-running process; full reasoning is on the Deployment page.

Not sure which host to pick? Email [email protected] with your budget and country — we send back 2–3 matched options before you commit to anything.

What you get

Platform admin console

The /admin route — workspaces, users, plans, subscriptions, queue health, impersonation, audit trail.

Plans & Stripe sync

Define the pricing tiers your workspace owners subscribe to. Stripe stays in sync automatically.

Architecture

Stack, data model, RAG pipeline, hot path, multi-tenancy, security — the full picture under the hood.

Deployment

Production rollout, queues, caches, rolling restarts, zero-downtime upgrades.

Environment

Every .env key explained — what's required, what's optional, what each toggle does.

Observability

Logs, traces, metrics, alerts — and how to wire them to your existing stack.

Your first day

  1. Set the environment variables — DB, mail, Stripe keys, app URL.
  2. Deploy to your production host (Plesk, VPS, container — your call).
  3. Grant yourself super-admin via tinker, then open /admin.
  4. Create your pricing plans and sync them to Stripe.
  5. Open the Users docs from your visitor's perspective to make sure the signup → workspace → embed flow works end-to-end.

Ongoing operation

  • Health — queue depth and failed jobs are the early warning. Retry policies are documented there too.
  • Support — impersonation lets you reproduce any workspace owner's bug without asking for credentials. Audit trail keeps you covered.
  • Upgrades — track the application changelog, then follow the deployment procedure.
  • Scale — read Hot path & latency before tuning workers, Redis, or the AI provider.

Supporting your users

Your workspace owners read the Users track. If they ask you a question about agent setup, the widget, knowledge sources or billing flows, point them there first — then dig in through impersonation if a real bug surfaces. The API reference is shared between both tracks; you'll need it if a user pushes content via the ingest API or wires up custom webhooks.