One portal. Status, incidents, tickets, docs.
Everything your customers need to know about your product — at one URL, branded as yours.
Status page, support tickets, help docs, API reference, changelog — one place for customers, not five.
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.
Not a ticket login. The whole customer-facing side of your product.
Most "customer portals" are a login page where customers check their tickets. Useful — but it's one feature.
StayUpfront's portal is everything your customers see of you: live status, what's broken and what you're doing about it, the tickets they've raised, your docs, your API reference, what you've shipped. One URL — the page they bookmark, and the one place that answers "is it just me, and are you on it?"
What your customers see when they go to your portal.
Seven surfaces, one URL — all of it ships with every portal. And a label on replies written by Una.
Live status, ninety days of history.
One banner for right now, components broken out, and ninety days of uptime bars anyone can audit.
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.
An active incident sits at the top of the portal — affected components, current status, your latest update.
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 — theirs, and their colleagues'.
Customers see every ticket their company has raised, not just their own — and your support hours show right on the page.
Read moreYour tickets
New ticketSupport is open now · closes 18:00 GMT
Can we raise the webhook rate limit on our plan?
SSO login redirect loops on staging
CSV export missing the new columns
Docs, on the same portal.
Help articles and product docs next to your status and tickets — searchable, and visible to exactly who you choose.
Read moreGetting started
Getting started with the API
Create a key and make your first call.
Setting up webhooks
Receive events as they happen.
Rate limits explained
What the limits are and how to raise them.
Your API reference, with a Try-it console.
Upload an OpenAPI spec and the portal renders a full reference — guides, an API changelog, and a Try-it console.
Read moreDeclare a new incident on a component.
"title": "Elevated error rates",
"severity": "major"
}
What you've shipped lately.
Release notes on the same surface, with a public roadmap alongside — customers follow a feature and hear when it ships.
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.
A public feed anyone can follow, plus a personal one for signed-in customers scoped to what they can see.
Subscribe
Public feed
Your personal feed
Feed content
Una's replies are labelled.
When Una sends the first acknowledgement on a ticket, the reply carries the bot icon and the name Una — so customers know it came from Una, not a person on your team.
More about UnaOne rule everywhere: control who sees what — public, signed-in customers, or specific accounts — and it applies across every surface.
Your URL. Your logo. Your portal.
From your 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 only what's relevant on each portal — uptime history, active incidents, changelog, and more.
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.
A portal is made of whichever components you choose to show. Run one portal for everything you sell, or one per product — each with its own components, domain, logo, changelog, docs, and subscribers.
Your team works in one workspace behind all of it, with role-based permissions per area — the person answering tickets doesn't have to be the person who can touch billing. Your customers see only what's theirs.
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.
StayUpfront is nearly ready, and I'm bringing in founding customers first — a small group at a time, so I can work with each of you on what the portal becomes. Founding customers get founding-customer pricing, a real say in what gets built, and a personal onboarding call with me.
Drop your emailDirect email from Rob when your slot's ready. No drip sequence.