Zephyr gives operators one serious workspace for node capacity, appbox provisioning, customer handoff, support, requests, and deployment state. It replaces the messy gap between billing, scripts, screenshots, and memory.
Tracked alongside customer context, request state, and support load.
Visitors should understand what the product is, what the operator workflow looks like, and how a real setup gets from blank server to customer handoff. The public experience should remove doubt instead of creating more questions.
Portal handoff, better docs, and a clearer operator workflow reduce the basic questions that should never reach you.
The panel, demo workspace, and handbook now mirror each other so new operators can learn the actual workflow instead of asking how each page fits together.
A real landing page, richer docs, and product-aligned screenshots make the platform look and behave like a serious service from first click.
These framed previews come from the public demo routes. What prospects see on the site lines up with the panel they open next.
Track real deployment movement instead of guessing why a service is still starting.
Let prospects click around safely without touching production state.
Use visuals that match the live panel instead of stale marketing art.
The point is not adding random widgets. It is reducing hidden work: fewer side tools, fewer manual deployment steps, and fewer support loops caused by poor visibility.
Spin up customer appboxes with the right image, resources, node placement, ports, and mounted paths instead of babysitting each server by hand.
Track fleet capacity, version drift, and node health in one place so deployments land on servers that actually have room to run them.
Keep customer records, linked appboxes, stream allowances, and service ownership tied together instead of scattered across scripts and notes.
Give every customer a portal with their URL, credentials, setup guidance, and ticket access so basic onboarding stops becoming manual support.
Track content requests and automation status from the same panel operators already use for services, support, and deployment history.
Handle Cloudflare Tunnel, node connectivity, and network-aware service placement without treating routing as a separate side project.
Open tickets with the customer, appbox, and node context already visible so your replies start with diagnosis instead of guesswork.
Keep products, plans, provisioning, and external workflows aligned through WHMCS and API-driven automation instead of repeated manual changes.
The handbook is now written like an operations layer: setup recipes, deployment checks, handoff flow, node troubleshooting, and screenshots taken from the product itself.
One-command node installation for Debian and Ubuntu, Docker bootstrap included, with guidance for re-installs and stale agent cleanup.
Portal-first onboarding, credential checks, app guidance, and delivery steps that catch issues before the customer opens a ticket.
Provisioning failures, routing checks, agent drift, and node verification steps written around the real panel behavior instead of theory.
Use the docs as the front line for new staff, new servers, and customer handoff. The goal is to answer routine operator questions before they become a ticket or a DM.
Every plan includes unlimited appboxes. The main variable is how much fleet you want Zephyr to control.
All plans include the operator panel, customer portal, API access, deployment workflows, and integration support.
Good operator platforms reduce ambiguity. Zephyr follows a clear sequence so staff can move faster and customers get a cleaner handoff.
Create a node in the panel, copy one install command, and bring a fresh Debian or Ubuntu machine online with Docker and the agent configured.
Define the runtime shape you want to sell: app type, stream rules, transcode expectations, resources, and deployment defaults.
Pick the customer, pick the product, and let Zephyr place the workload on the best available node with the right routing and service metadata.
Send the customer to their own portal page with access details, setup guidance, and the correct support path instead of typing the same instructions again.
Track node health, provisioning progress, support, requests, and customer state from one control plane instead of several half-connected tools.
Zephyr is the control plane for hosted media operations: node registration, product templates, customer appboxes, provisioning, support, requests, and handoff.
Yes. The landing page and docs use framed previews from the interactive demo workspace so the visuals stay aligned with the actual product.
That is the goal. The docs now focus on repeatable checklists, daily operating routines, and common failure paths so the platform is more self-serve.