# Dashboard v5 — rebuilt around fleets, with the same API underneath
Source: https://proxuno.com/blog/introducing-dashboard-v5
Updated: 2026-06-23

> Version 5.0 is a complete redesign of the customer dashboard. Why we rebuilt it, what changes in daily use — fleet tables, bulk actions, a real overview page, dark mode, phones — and what deliberately stays the same.

Today we are releasing **version 5.0** of the platform, and with it a completely redesigned customer dashboard. It is the largest change to the interface since 2022. The public API, credentials, ports and rotation links do not change at all.

This post explains why we rebuilt it, what is different, and what we deliberately kept.

## Why rebuild

Dashboard v2, released in November 2022, was designed for customers with a handful of mobile proxies in one or two countries. Since then the platform has grown three product lines, ten mobile countries, a prepaid balance, auto-renewal and an affiliate programme — each added as another page or another tab.

Usage changed even more. Many accounts now run fleets of dozens or hundreds of proxies across several countries and carriers, alongside residential traffic and static IPs. The questions they ask the dashboard are fleet questions:

- Which proxies expire this week, and which of them will auto-renew?
- How much residential traffic is left, and at the current rate, when will it run out?
- Which of my German proxies are on 5G right now?
- Give me the credentials of every Italian proxy, as one list.

The old interface answered these one proxy at a time. Version 5 answers them on one screen.

## What changes

### An overview that is actually an overview

The first page now shows what needs attention: proxies expiring in the next days (and whether they will auto-renew), residential traffic remaining with its expiry, current balance, recent orders and the latest platform changes. Most customers should be able to check their account health without opening another page.

### Fleet tables

Mobile and static proxies are listed in dense, sortable tables showing country, carrier, current IP, radio technology, rotation schedule, expiry and auto-renew state. From the same table you can:

- filter by country, carrier, status and expiry window;
- select many proxies and renew them with one invoice;
- copy the credentials of the selection in one block;
- jump to any proxy's detail page.

### Proxy detail

Each proxy has a single page with its credentials, rotation controls (button, schedule, rotation link), rotation history with old and new addresses, and usage. The rotation link and the password can be regenerated from there.

### Residential, in one place

The residential page combines your packages and their expiry, daily usage charts, the endpoint generator for ready-made credential lists and your residential login details.

### Billing that matches how people pay

Balance, top-ups, orders and invoices sit together. Since October 2025, most renewals are paid from balance; the new layout makes the balance and auto-renewal state visible wherever a decision about renewal is made.

### Dark mode, keyboards and phones

The interface follows your system theme, with a manual override. Every table works with the keyboard, focus is always visible, and every page — including the purchase configurator and the crypto payment page — works at phone width. A surprising share of rotations and renewals happen from phones, and v2 handled that poorly.

## What deliberately stays the same

Redesigns often break things that customers rely on. We set ourselves strict constraints:

- **The API is unchanged.** Every v1 endpoint, field, status code and error code behaves exactly as before. Your scripts need no changes.
- **Credentials are unchanged.** Hosts, ports, usernames, passwords and rotation links keep working; nothing is regenerated by the upgrade.
- **URLs are stable.** Dashboard addresses for proxies, orders and settings stay where they were, so bookmarks and links in internal runbooks keep working.
- **Prices and policies are unchanged.** The redesign is not a pretext for new fees or new limits.

## How we built it

The new dashboard is server-rendered, with small amounts of JavaScript for interactions such as copying, filtering and charts. That keeps pages fast on slow connections and lets every page work before scripts load. We tested it with long translated strings, at narrow widths, in both themes and with keyboard-only navigation before release.

We also ran v5 alongside v2 for a group of customers who volunteered during the spring. Their feedback changed the design of the fleet table — particularly the decision to keep expiry and auto-renew state visible in every row — and the default sorting of the overview.

## Using the API for what the dashboard does

Anything you do in the fleet table can be automated. For example, listing proxies with their current IPs:

```bash
curl -H "Authorization: Bearer $PXL_KEY" \
  "https://{{domain}}/api/v1/proxies?limit=100"
```

API keys are managed from the API page of the dashboard. A key is shown once at creation; store it in your secrets manager.

## What comes next

Version 5 is a foundation. Already planned for the coming releases: labels on proxies with search and filters, usage charts by target country, and more export formats for credential lists. Each will be listed in the [changelog](/changelog) as it ships.

If anything you relied on in v2 is harder to do in v5, tell support. Several improvements in this release started as a single customer message.