Frontend publishing and traffic controls

Publish pushed code, inspect deployments, understand deployment warnings, and read production traffic measurements.

8 min readUpdated Sep 29, 2026

Step-by-step guidance.

Before you start

Open the named screen in Rumata. Available controls may depend on your account, permissions, and resource state.

Open System Explorer → Frontend. This screen manages the published website and its production traffic.

Control	What it does
Visit live site	Open the published address in a new tab. Available when the frontend is deployed and has an address.
Open code	Switch to the code view for this factory.
Manage deployments	Open publishing settings and recent deployment history. Opening this dialog does not publish.
Deployment status	Read whether publishing is in progress, deployed, failed, or otherwise unavailable. A completed prior deployment can remain live while you inspect new work.

Deployment builds the latest pushed Git commit. Saving a file in the editor or seeing it in preview is not sufficient to publish it.

Control	What it does
Website address	Choose the site-name portion of the displayed deployment address. Production currently shows .sites.rumata.dev; use the suffix displayed in your environment. The field is disabled during an active deployment.
Deployment URL / copy icon / external-link icon	Read, copy, or open the address shown in the dialog. If you edit Subdomain, these controls reflect that draft address; it is not evidence the new address is live.
App workflows / Review deployment / Deploy project	Choose the workflow versions to publish with the website. Review deployment checks the pushed source and selected workflows; Deploy project starts the reviewed release. Read warnings before confirming.
Reviewing workflow versions / Checking / Deploying	Wait for the current step to finish. A queued deployment is not a successful deployment; check its final status and any failure reason.
Close / Cancel / corner X	Dismiss the dialog. This does not undo a deployment already queued.
Undeploy	Take the frontend offline immediately. This button sends the request directly, without a second confirmation in this dialog.

Some deployments need an extra decision before they can proceed.

Control	What it does
Paid AI warning → workflow row	Open that workflow to review who pays for its AI feature. Publishing can let other people trigger those charges.
Back to settings	Stop this publishing attempt so you can review billing and access settings.
Paid AI review → Deploy project	Continue with the reviewed deployment, including the listed paid-AI workflows. If visitors can invoke them, usage may charge the configured payer. This action does not configure budgets, change the payer, or fund anonymous visitors.
Private workflows / Future workflow saves / Shared workflows	Review which features remain unavailable to visitors, which workflows follow their latest saved version, and which changes also affect other factories. Pin workflow versions when future saves should wait for a separate release.
No new website changes → Back to settings	Return to update, commit, and push the intended changes before deploying again.
No new website changes → Deploy project	Rebuild the already-pushed version. Unsaved or unpushed changes are still excluded.

Use deployment history to check which code version was published and when.

Control	What it does
Copy commit SHA	Copy the full Git identifier shown beside a deployment.
Deployment status / failure reason / asset size and file count	Inspect the outcome and generated site files. Retired identifies a previous deployment that is no longer the active version.
Retry workflow activation	Retry selected workflow activation when the website is deployed but workflow activation needs attention. Read the failure reason first, then verify the live customer task after retrying.
Analytics on a deployment	Open traffic measurements for that version’s active production window, when available.
View frontend analytics	Open traffic for the frontend as a whole.
Back to deployments / analytics Close	Return from the analytics detail view.

One page visit often requests many files. The allowance counts HTTP edge requests rather than visitors or page views.

Control	What it does
Hourly / Daily	Group traffic points by hour or day.
7d / 30d / 90d	Choose the requested lookback for frontend-wide analytics. Your plan can shorten the available history. A specific deployment uses its active window instead.
Refresh	Reload analytics. The screen also refreshes about once a minute.
Traffic chart point hover	Read served and rate-limited requests for the selected time bucket.
Top locations → country row / map country	Select a location on the traffic map and inspect its request information.
Request origins → help icon	Read how locations are determined and when traffic may be sampled.
Shared allowance / served requests / 429 / server errors / bytes / average response	Compare the account-wide request allowance with this frontend or deployment’s traffic. Bytes and response time describe traffic but do not reduce the request allowance.