Portal changelog
The web app for customers and node operators: accounts, projects, tokens and payouts.
Operators with no check-in for 7 days now leave every leaderboard
Metro leaderboards and top-5 lists kept showing operators whose nodes had stopped checking in, some since June. Every board now lists only operators whose nodes have genuinely checked in within the last 7 days.
Claim your own domain in the portal and get its certificate automatically
Each deployment target with a custom domain now has a Custom domain block in the portal. Claim the domain, add the TXT and CNAME records it shows, and the certificate is issued once they are found. An unverified claim lapses after 48 hours.
The portal menu matches your view from the first page after sign-in
After signing in, operators could see the customer menu on their first page, and a passkey sign-in on a new browser opened Workloads. Both now follow the view saved with your account, and the menu highlights the page you are on.
Node offline emails are now actually being sent
The node offline emails announced on 1 October were not going out, because their wording was still marked as awaiting review. They have been sent since 4 October, including to operators whose accounts predate the current sign-up form.
A public status page at status.evolvingedge.ai
You can now see whether our services are up at status.evolvingedge.ai. It checks the control plane, the portal, sign-in and our own sites every minute, and the changelog shows live status badges above its entries.
Node locations now come from a database we host, not an outside lookup
Your node's city and metro are now looked up in a database we run ourselves, so its IP address is no longer sent to an outside service. Every node was located again on 2 October, so your place on the map and metro leaderboard may have moved.
Get an email when your node goes offline
When one of your nodes stops checking in for 15 minutes for a reason on your side, you'll get an email, and another once it's back. Outages caused by us are filtered out, and you can turn the emails off in Settings.
Smaller changes — a map caption, docs links, and a demo page removed
Three small changes, collected. The network map caption now says what the ee mark means, portal and email links point at the new docs addresses, and the edge node's built-in demo no longer has a Network page that couldn't work.
Portal deploys now check your _redirects file before publishing
A _redirects file deployed from the portal was published unchecked, so a mistake showed up only as a rule that quietly did nothing. The portal now checks it the way ee-cdn-cli does, and an error stops the deploy, naming the line.
Signing in takes you to the part of the portal you use
Signing in on a new browser or device always opened Workloads, even for node operators. The portal now remembers your view with your account, and otherwise goes by what you chose at sign-up, so operators land on their dashboard.
The network map shows the gateway nodes in 47 U.S. markets
The public network map now marks each of the 47 U.S. markets where Evolving Edge will operate gateway nodes, alongside the live node counts.
Smaller changes — nav links, and a build link that no longer 404s
Two small portal changes, collected. The public leaderboard nav now links to the blog and the changelog, and the CI deploy card has stopped showing an alias URL that returned 404.
A manually forwarded port now counts toward gateway eligibility
Operators who had forwarded a port by hand were still told to forward one. The eligibility check only looked at endpoints discovered by UPnP, and ignored the address the control plane was already recording from every heartbeat.
The deploy preview link now points at a host that serves it
Every deploy without a custom domain showed a preview link that returned 404, because the link named the edge node rather than the control plane. Deploys with a domain were unaffected, which is why it went unnoticed.
The monthly close now produces a statement, not a payment
The monthly close now works out what you earned and stops there, rather than moving money. Referral bonuses stay in your balance instead of being attached to a payout, and nothing is paid until a withdrawal is requested.
Level 2 content now opens only for people you authorise
Level 2 exists so we can decrypt your content for people you have approved. It did not work — the key travelled inside the page and access checks refused everyone — so in practice anyone with the link could read it. Access is now granted one person at a time.
Revoking a deploy token now confirms it worked
Revoking a deploy token left you on a plain error page saying the token was not found, with no sign the revocation had worked. You are now returned to your tokens list with a message confirming which token was deleted.
Level 1 decryption keys never reach our servers
Level 1 means only you, and whoever you share your link with, can read your content. Two faults broke that — one left the key on our servers, the other handed back no key at all. Both are fixed, and we now keep no copy of your key.
Referrals now qualify on real connected uptime, for both operators
Referral qualification now counts real connected uptime — 1,440 hours on a single node — and both the referrer and the operator they referred have to reach it. Everyone's hours start again from zero, so the earliest any referral can qualify is around mid-November 2026.
Passkey sign-in to the portal works again
Signing in to the portal with a passkey failed for several weeks, because a security certificate one of our sign-in domains depends on had expired. Password sign-in kept working throughout, as did nodes and the sites they serve.
The dashboard's Docker setup guide link now opens the guide
On the dashboard's node install card, the Docker tab's "Docker setup guide" link led to a page that didn't exist. It now opens the Docker section of the installation guide.
Deploy tokens keep every role you select
A deploy token created with both roles ticked lost its workload role, so every deploy with it was refused with "Insufficient permissions". New tokens keep every role you select. If you have a token affected by this, create a new one.
Metro leaderboards show a podium, each node's score breakdown, and work on phones
The metro leaderboards now put the top three nodes on a podium, let you expand any node to see how its Performance Index is made up, and turn into cards on a phone. Two score components that were labelled wrongly now carry the right names.
New operators appear on the Community page within minutes
A new operator's first node went live immediately, but the Community page could take up to an hour to list it, and until then said they had no nodes. It now catches up within a few minutes, and says your node is syncing while it waits.
Card titles on the Workloads page are readable again
A styling conflict made some portal headings near-black on a dark background, most visibly the Content Delivery card title on the Workloads page. All 18 affected elements are fixed, and a test stops the conflict coming back.
Sites deployed from CI now appear in the portal
Sites published from CI or the command line served normally but left the portal's Files and Deployments tabs empty, and their traffic was missing from project analytics. New deploys now show up in the portal just as portal deploys do.
Docs and Support are one click away in the portal
The portal's top bar has a new Resources menu with links to Docs and Support. It opens the guides for whichever view you're in, Node Operator or customer, in a new tab. Available on desktop.
A new account menu and an always-visible view switcher in the portal
Your profile, account settings and sign-out now sit in a menu under your name, and the switch between the Node Operator and customer views is always shown. The Refer page also links the referral program terms directly.
Dashboard cards now open Earnings, the Leaderboard and your profile
The Earnings & Payouts, Local Leaderboard and Performance Index cards on the dashboard were dimmed and marked "Coming soon", though all three features were already live. Each card is now a link to its page.
Refer other operators from the portal
Operators now have a personal referral link and a Refer page in the portal. When someone you refer keeps a verified node online for 60 days, you both earn a bonus. There's no cap on referrals.
Healthy nodes no longer show single-digit uptime
When a node's activation date was missing, its uptime was measured against a full 30 days, so a node with two perfect days showed 6.67%. Uptime is now measured against the time we actually observed the node.