# Frontend
Monitor your live website, track traffic, and manage deployments—all from your Rumata workspace.
Source: https://docs.rumata.dev/guides/system-explorer-frontend
Reviewed: 2026-09-29
## About Frontend
The **Frontend** section in System Explorer gives you visibility and control over the published version of your application.
You can monitor website activity, review resource usage, manage deployments, and troubleshoot failed releases without switching between platforms.
Whether your website was built with Rumata's AI agent or customized through code, you can manage its live version here.
## Before you start
Open your factory workspace and navigate to **System Explorer → Build → Frontend**.
If your application hasn't been deployed yet, some monitoring information may not be available.
## 1. Explore your Frontend
The **Frontend** section is where you can check your live website's status and access its deployment and monitoring tools.
Open your Frontend
1. Go to **System Explorer → Build → Frontend**.
2. Review the deployment badge and current frontend status.
3. Click **Visit live site** to open your published website, if available.
4. Select **Open code** if you want to inspect the frontend's source code.
> **Good to know**
> Your live website and your development preview are different environments. Changes made in Preview don't automatically update your published website.
## 2. Monitor your website traffic
Once your website is live, Rumata provides analytics to help you understand its activity and performance.
Explore your frontend analytics
1. Open **Frontend** in System Explorer.
2. Choose **Hourly** or **Daily** to control how traffic data is grouped.
3. Select a time range: **7d**, **30d**, or **90d**, depending on your plan's available history.
4. Click **Refresh** to update the displayed statistics.
5. Review the available performance and traffic metrics.
Understand your website metrics
**Requests served**
See how many requests your website has received. These requests count toward your account's shared edge-request allowance.
**Rate-limited requests (429)**
Track requests that were restricted because a request limit was reached.
**Server errors**
Identify requests that encountered server-side errors.
**Response bytes**
See how much response data your website delivered.
**Average response time**
Understand how long your frontend typically takes to respond to requests.
**Request origins**
Explore where requests to your website are coming from using the geographic view and time chart.
Requests vs. visitors
**Website requests are not the same as page views or unique visitors.**
When someone opens your website, their browser may request multiple resources, including HTML, JavaScript, stylesheets, images, and fonts.
Each of these can count as a separate request. This means one page visit can generate several requests.
Response size and response time are separate measurements and don't reduce your request allowance.
Check your result
You should now be able to see your website's activity, review errors and response times, and understand how traffic contributes to your usage.
Production frontend analytics and release-management controls. Illustrative interface reference; your resources and values may differ.
## 3. Manage your deployments
The **Manage deployments** section lets you review your published releases and prepare new ones.
Open deployment management
1. Go to **System Explorer → Build → Frontend**.
2. Click **Manage deployments**.
3. In the **Deploy Project** window, review your **Website address** and available deployment information.
4. Check the frontend source status and any backend services or workflows included in the deployment.
5. Open **Recent deployments** to review previous release attempts.
Understand deployment history
Each deployment attempt may include information such as:
- **Status:** Whether the deployment succeeded, failed, or was retired.
- **Timestamp:** When the deployment was attempted.
- **Commit:** The source version associated with the deployment.
A previous successful deployment doesn't necessarily mean the latest deployment was successful.
> **Good to know**
> Reviewing deployment settings doesn't publish changes. You must explicitly confirm a new deployment before it goes live.
Review your website address, included services, and deployment history in Deploy Project.
## 4. Publish updates to your website
As you continue improving your application, you can publish new versions without starting from scratch.
Deploy an updated version
1. Make your changes in your factory workspace using Rumata's AI agent or by editing the code.
2. Test the updated application in **Preview Mode** to make sure everything works as expected.
3. Open **Frontend → Manage deployments**.
4. Review the **Website address**, selected services, workflows, and available settings.
5. Click **Review & deploy** to open the deployment review.
6. Check the selected components, build options, capacity, and any warnings.
7. If everything looks correct, click **Deploy now**.
8. Monitor the result in **Recent deployments**.
9. Once the deployment succeeds, click **Visit live site** and test your application's main features.
Check your result
Your updated application should be available at its public website address, with the intended changes working correctly.
> **Tip**
> If you need to adjust anything during the deployment review, click **Back to settings** before publishing.
For a complete walkthrough, see [Publish your app](https://docs.rumata.dev/guides/publishing).
## 5. Troubleshoot failed deployments
If a deployment doesn't succeed, Rumata provides information to help you understand what went wrong.
Investigate a failed release
1. Open **Frontend → Manage deployments**.
2. Find the failed attempt under **Recent deployments**.
3. Review the reported error and available details.
4. Identify whether the issue relates to the frontend build, backend resources, workflow activation, or another reported cause.
5. Ask Rumata's AI agent to help investigate the specific error, or resolve it manually.
6. Review your deployment settings and retry once the issue is fixed.
7. After a successful deployment, open the live website and test the affected functionality.
> **Important**
> Don't assume your latest changes are live just because your website remains accessible. Confirm that the intended deployment succeeded and that the new version is available at the public address.
## Keep your website running smoothly
With Rumata, publishing your application is just the beginning.
You can continue building with AI, monitor real website activity, track performance, investigate issues, and release improvements—all within the same platform.
Your development workspace and published application stay connected, giving you a consistent place to build, deploy, and manage your software.
## Related guides
- [Frontend publishing and traffic controls](https://docs.rumata.dev/guides/controls-frontend)