One portal. Status, incidents, tickets, changelog.
Everything your customers need to know about your product — at one URL, branded as yours.
Not a login page where customers chase tickets. A surface that shows what's working, what isn't, and what you've shipped lately.
Dashboard loading slowly for some customers
InvestigatingIdentified a slow query from today's deploy and rolling it back. We'll confirm here once load times recover.
Posted
v2.4 — Better filtering in saved views
Saved views now support multi-condition filters, so you can pin the exact slice of tickets your team works from.
When we say "customer portal," it's likely not what you're picturing.
Most "customer portals" are a login page where customers check the tickets they raised with you. Useful — but it's one feature, not the whole surface.
StayUpfront's customer portal is the whole customer-facing edge of your product. It shows your customers what's working right now, what's broken and what you're doing about it, the tickets they've raised with you, what you've shipped recently, and how to be told when any of it changes. One URL. Custom-branded. The page they bookmark.
And when someone logs in, they see every ticket their company has raised with you — not just their own. So a colleague picking up the thread already has the history, instead of starting a fresh ticket from scratch.
Your customer's Tuesday looks different.
They notice the dashboard is slow. They check your status page — bookmarked from the last time something broke — and it says "all systems operational" from 6 weeks ago, because nobody's owned updating it.
They open the support widget, can't find their last ticket, and start a new one. Two days later you reply and ask if they've tried a hard refresh. They say yes. You ask which browser. They've forgotten.
Meanwhile your changelog lives on a Notion page that 404s in incognito. Your release notes are in a monthly email they don't remember subscribing to. The thing they actually wanted — "is this just me, and are you on it?" — was never on any of those surfaces.
What your customers see when they go to your portal.
Five surfaces, one URL — and a label on AI-authored replies. All of it ships with every portal.
Live status, ninety days of history.
A green/amber/red banner for right now, components broken out, and ninety days of uptime bars that anyone can audit. Driven by your actual incidents — not a separate manual process.
Read more90-Day Uptime
99.8%Dashboard loading slowly for some customers
InvestigatingIdentified a slow query from today's deploy and rolling it back. We'll confirm here once load times recover.
Posted
Whatever's broken right now, and where you are with it.
When an incident's active, customers see it at the top of the portal — the affected components, the current status (investigating, identified, monitoring), and your latest update. No tweet to find, no Slack channel to join.
Read moreDashboard loading slowly for some customers
InvestigatingUpdates
Identified a slow query from today's deploy. Rolling it back now — we'll confirm once load times recover.
We're seeing elevated load times on the dashboard for some customers and are investigating.
Tickets the customer raised, in one place.
Customers raise tickets, reply to them, and see the whole company's history without leaving the portal — every ticket their colleagues raised, not just their own. Status pills show where each one stands. The team's internal notes stay internal.
Read moreYour Support Tickets
New TicketCan we raise the webhook rate limit on our plan?
SSO login redirect loops on staging
CSV export missing the new columns
What you've shipped lately.
Release notes published to the same portal, carried in its Atom feed, with a per-portal toggle. No more "we have a changelog somewhere" — it's the same surface.
v2.4 — Better filtering in saved views
Saved views now support multi-condition filters, so you can pin the exact slice of tickets your team works from.
Webhook retries with backoff
Failed webhook deliveries now retry automatically with exponential backoff, and you can replay any delivery from the logs.
Faster status page loads
Rebuilt the uptime history rendering — status pages now load noticeably faster on large component lists.
Customers subscribe themselves.
Email and Atom-feed subscriptions, scoped to the components your customer cares about, with a personal feed URL they can regenerate. The customer decides what they want to know about — you don't have to maintain a list.
Notifications
Public feed
Your personal feed
What you hear about
When Sue replies, she's labelled.
Some replies your customers see come from Sue — the AI inside StayUpfront. When she sends the first acknowledgement on a new ticket, she's labelled: the bot icon and her name, so it reads as Sue and not a faceless "system" message.
More about SueDocs are coming to the same portal.
Help articles and product docs, on the roadmap — published to the same portal, sitting right next to the status, incidents, and tickets your customers already see. One place to find out what's happening and how something works, instead of a docs site that lives somewhere else entirely.
Your URL. Your logo. Your portal.
Out of the box, your portal lives at yourcompany.stayupfront.com. To put it on a domain you own — support.yourdomain.com, or whatever subdomain you pick — you point a CNAME at us and it's yours. Certificates for secure connections are provisioned and renewed automatically; you never touch them. Your logo (square or landscape, dark or light variants) renders across every surface — status, incidents, tickets, changelog. From the customer's point of view, it's a page on your product, not a page on ours.
Custom domain. support.yourdomain.com or any subdomain you own — point a CNAME at us. Certificates are handled for you.
Logos. Square logo, landscape logo, dark and light variants. Your customers see your brand, not ours.
Per-portal display toggles. Show or hide the uptime history, the active incidents section, the changelog — depending on what each portal is for.
Dashboard loading slowly for some customers
InvestigatingIdentified a slow query from today's deploy and rolling it back. We'll confirm here once load times recover.
Posted
Same back office, two portals.
One portal for everything, or one per product. Your call.
The building block is the component — the thing with the uptime bar, the part of your product that can be up or down. A portal is made of whichever components you choose to show on it. Your organisation's components can all live on one portal, or be split across several. Both are first-class; neither is the "real" way.
So you can run one portal that covers everything you sell — or a separate portal per product, each with its own components, its own changelog, its own custom domain, its own subscribers. Show whichever components matter on each portal. Your team works in one internal workspace across all of it; your customers see only what's theirs.
Whichever shape you pick, each portal carries the whole surface — live status, incidents, the changelog, and (on the roadmap) docs — from one internal workspace and one data model. One bill. One team. One context.
Webhook deliveries are failing
InvestigatingWebhook deliveries are failing for some endpoints. We've identified the cause and are rolling out a fix — we'll confirm here once deliveries recover.
Posted
Two products, two portals, one internal workspace.
I built the portal as the thing — not a feature bolted onto a support tool. It's what your customers actually experience of your product: the face of it. So it couldn't be an afterthought. It had to be the part that's right. One URL, branded as yours, where the surfaces that matter — status, incidents, tickets, what you've shipped — live together. If it doesn't feel like a page on your product, nothing else I build matters.
— Rob Gough, Founder
What's powering each surface.
The portal is what your customers see. These are the workflows behind it — each has its own page.
Want this for your customers? Get in early.
Private beta in a few weeks. I'm letting people in a small group at a time so I can actually work with each of you — what's working, what isn't, what to ship next on the portal. The earliest customers have the most influence on what this looks like for theirs.
Drop your emailDirect email from Rob when your slot's ready. No drip sequence.