Public Status Pages for Small Teams: The Sharing Loop That Grows Your Brand

When a customer notices your app is slow, the first thing they do is check whether you know about it. If there's no public status page, they open a support ticket. That ticket gets routed, triaged, and eventually answered — usually after the problem is already resolved. The customer's experience: poor communication. Your team's experience: unnecessary support load during an incident.

A public status page solves this. But for small teams, it also does something more interesting: it becomes a quiet acquisition channel.

The Sharing Loop

Here's how the loop works:

1. You share your status page URL with customers or in your app's footer
2. A potential customer sees the link, visits it, and sees "Operational — 3 machines, all healthy"
3. They notice it says "Powered by tink.bot" (or just that the infrastructure seems monitored)
4. They remember that when they need monitoring for their own servers

This isn't hypothetical. Every Statuspage.io-powered status page you've ever seen has this effect at the bottom — "Powered by Atlassian Statuspage." At $29/month per component, Statuspage has built a significant portion of its brand through customer status pages that reference it.

For small teams using Tink, this creates a natural referral surface without any additional work.

What Makes a Status Page Actually Useful

Most status pages are useless during incidents because they're maintained manually. The engineer who's most needed to fix the problem is also responsible for updating the status page. In practice, they update it once the incident is resolved, which is too late to be useful.

The only status pages that work during incidents are the ones that update automatically.

Tink's public status page (/status/[userId]) pulls live data from your Tink account — health scores, open issue counts, last-seen timestamps — all without requiring manual updates. When a machine goes from healthy to critical, the status page reflects that in the next scan cycle (minutes, not hours).

What it shows:

• Overall fleet status (Operational / Degraded / Outage)
• Machine list with health scores and issue counts
• Last-seen timestamp per machine (so customers know data is current)

What it never shows:

• IP addresses or hostnames beyond what you've named machines
• Credentials, tokens, or internal config
• Log content or security scan results

The sanitization is deliberate. A public status page communicates health without leaking sensitive infrastructure details.

Who Should Share a Status Page

Not every team needs one. But if any of these apply, it's worth five minutes to set up:

• You have customers who care about uptime (SaaS products, API providers, managed services)
• Your clients ask "is it down?" during incidents and you're tired of responding manually
• You're positioning your service as reliable and want a tangible proof point
• You're a freelancer managing client infrastructure and want a professional touch without the Statuspage.io bill

The last case is underrated. A freelancer who sends their client a link to a live status page is presenting themselves differently from one who sends a manual email saying "everything looks fine." One is passive and forgettable. The other is professional and memorable.

How to Get Your Status Page

In Tink, your status page is available at https://tink.bot/status/[your-user-id] — no setup required. You can find the direct link in the account console under Public Status Page.

Two buttons: Copy (for sharing) and Preview (to see what your customers see before sending it anywhere).

The page requires no authentication to view. That's the point — it's for customers and stakeholders who don't have Tink accounts.

The Limitation Worth Acknowledging

The current status page shows live state, not historical uptime. If you want to show "99.7% uptime over the last 90 days," that's not there yet — it's on the roadmap. For now, the page gives a current health snapshot, which is more than most small-team infrastructure has ever offered their customers.

For most use cases, current-state transparency beats historical percentage theater. Customers care whether you're having a problem right now, not whether your three-month average was impressive.