Customer docs where your customers already are.
A knowledge base published straight to the same branded portal as your status page, your incidents, and your support tickets. One place your customers go for answers — not a fifth tab nobody can find.
One source of truth, not a second one to keep in sync.
What a knowledge base is
A knowledge base is where your customers find answers themselves, without writing in and waiting for a reply — a help center, as most customers call it. (In StayUpfront, it's the surface we call Docs.)
The catch for small teams: it ends up a fifth subscription and a fifth login, bolted on next to the support tool, the status page, and the incident tool — none of which know it exists.
The trouble with a knowledge base off on its own
A standalone knowledge base doesn't know about the ticket your customer just raised, the incident you're in, or what your status page shows. So customers hunt across tabs, and during an outage the guidance they need sits one tool over from the page they came to for status.
- Getting started: your first 10 minutes
- Connecting your domain
- Troubleshooting sync delays
Your docs live where your status and support already do
In StayUpfront, Docs is one surface of the same branded customer portal that already carries your status page, your incidents, and your support tickets. One URL your customers learn once. One login, one bill, one data model — no fifth subscription, no second source of truth.
Customers find the answer before they write in. When they do write in, the agent answers with the article that already exists. And during an incident, the relevant guidance sits right there on the page they came to for status. The knowledge base isn't bolted onto the portal — it's part of it.
- Getting started: your first 10 minutes
- Inviting your team and setting roles
- Troubleshooting sync delays
- Connecting your domain
You don't need a docs team to have a help center
The big knowledge-base tools assume a knowledge manager and a content-ops process. A team of two to five doesn't have that — the person who'd write the doc is the same one answering the ticket and watching the monitors.
So the knowledge base has to be the kind of thing that exists without demanding a full-time owner: included with your account — no fifth bill, no per-seat pricing — on the same branded portal that already makes you look credible to a B2B buyer, and worth keeping current because it's the same place your team already works.
Where this is — honestly
This is already how StayUpfront is built — status, incidents, and tickets share one branded portal, and Docs is live in it today. Your customers get a searchable help center with a page for everything you publish, and you decide who sees what: public to the world, your customers only — down to specific customer groups — or internal to your team. And the whole thing is published as a markdown index, so LLMs and agents can read your docs too.
One portal for everything your customers need. Get in early.
Private beta is a few weeks out, and I'm letting people in a small group at a time. The earliest customers shape what ships next on the portal that already carries your support, status, and incidents.
Drop your emailDirect email from Rob when your slot's ready. No drip sequence.