Solution

Create a status page in five minutes

A page where customers can look it up instead of asking. Setting it up takes five minutes; running it costs nothing at all on the smallest plan.

Try LIVCK Cloud for free See pricing

Time to first page: under 5 minutes; account, service, component, branding, domain
Cost: €0, permanently; not a trial, no credit card
Live immediately at: statuspage.de; as your own subdomain; custom domain included in every plan
Subscriber channels: 6; email, webhook, Slack, Teams, Discord, Telegram

In short

A status page is the public page where customers see whether your services are running — and what you are doing when they are not. With LIVCK it takes five steps: create an account, put the first service under monitoring, place it on a page as a component, set logo and colour, connect a domain. The page is reachable immediately at yourcompany.statuspage.de; a custom domain takes two DNS records and is included in every plan. The free plan covers one status page, 20 monitored services and 250 notified subscribers — permanently, with no credit card and no expiry date.

What belongs on a status page?

The overall state, a short list of components, ongoing incidents, announced maintenance and the history of the past weeks. Nothing else. A status page is not an architecture diagram; it answers exactly one question: is it you or is it me?

The most important decision is what the components are called, and it comes before any styling. Components are named after what a customer is trying to do, not after what sits in your data centre. “Sign-in”, “Payments”, “File upload” answer the question. “api-gateway-eu-west” and “redis-primary” do not — they are accurate and still useless, because nobody outside your team knows which one is their problem.

Components can be grouped. A group “Web” with the children “Website”, “Console” and “Documentation” shows the summarised state at the top and the detail underneath for whoever wants it. That keeps the page short without dropping information.

Every component carries a state, and that state is computed rather than typed in: operational, degraded, partial outage, major outage, under maintenance. It follows the monitoring of the service behind it — so the page cannot say “all good” while the checks have been failing for an hour.

Operational: All checks pass. The normal state, shown ninety-nine percent of the time.
Degraded: The service answers, but not correctly — too slowly, or with a response that violates an assertion.
Partial outage: Some measurement locations or some components of a group are affected, not all of them.
Major outage: The service is unusable. The state visitors actually come to the page for.
Under maintenance: An announced window is running. Visible from the announcement until it closes, so nobody mistakes a planned restart for an outage.

Component list of a status page: the group “Web” at 100.00 % availability marked operational, with the individual components “Website” and “Console” indented below it, each with a 90-day availability bar. — Group on top, detail underneath — one page that stays short for both ways of reading it.

To maintain a state by hand, create the service with the check type “Manual”. No automatic check runs, and the state only changes when a human changes it — useful for anything that cannot be measured from the outside, such as a delivery service or a phone system.

How long does this actually take?

About five minutes to a publicly reachable page at yourcompany.statuspage.de. If you want a custom domain, add two DNS records and the usual wait until the change has propagated — usually minutes, at worst hours. That is the only waiting in the whole process, and it happens at your DNS provider.

The five minutes are not a marketing number but the sum of the steps below: roughly a minute each for account, first service, status page and components, two for branding and domain. What is not included is deciding which components to show at all — that reliably takes longer than everything technical put together, and it is worth it.

The free plan asks for no credit card and does not expire. So there is no reason to plan the process in advance: set it up, look at it, and rebuild the structure if it does not fit. None of it is one-way.

The result after five minutes: own logo, overall state, subscribe button.

How do I put it on my own domain?

With two DNS records. A CNAME points your chosen address at our edge, a TXT record proves the domain is yours. After that LIVCK issues the TLS certificate itself and renews it itself. A custom domain is included in every plan, the free one as well.

Why two records rather than one: a CNAME alone only proves that somebody pointed a domain at us. Somebody who does not own the domain can do that too. The TXT record is the actual proof of ownership, and the domain only goes active once both are correct.

Verification runs against four independent DNS resolvers in different jurisdictions, two of which have to agree. That sounds like a lot of effort for a DNS record, and it has a reason: a single resolver returning a wrong answer would otherwise be enough to pull somebody else’s domain into somebody else’s account.

Until the domain is active the page stays reachable at its statuspage.de address. There is no window in which nothing works — and anyone who never sets up a custom domain still has a working, public status page.

The two records you add at your DNS provider. The console shows the secret for the TXT record when you add the domain.
Type	Name	Value	Purpose
CNAME	status.yourcompany.com	edge.livck-status.com	routes your visitors to LIVCK
TXT	_livck-verify.status.yourcompany.com	the secret from the console	proves the domain really is yours

Do not put the status page on a subdomain of the domain it is supposed to monitor. If that zone fails, the page that should report the failure fails with it — the one case it exists for.

How do I make it look like my company?

Through logo, colours and custom CSS. You upload one logo for light mode and one for dark, set a primary and a secondary colour, and override anything beyond that with your own CSS. Imprint and privacy policy are linked, not rebuilt.

Two logos: One for light mode, one for dark. A single logo with dark lettering disappears for exactly those visitors who check at night.
Primary and secondary colour: Colour buttons, links and highlights. State colours are deliberately left alone — green and red mean the same thing on every status page, and they should keep doing so.
Custom CSS: For everything else: typography, spacing, header. There is no surcharge for it and no plan without it.
Favicon: Your own icon for the browser tab. A detail that shows the moment somebody leaves the page open — which is what people do with a status page.
Imprint and privacy policy: Two URL fields that appear in the footer. For a publicly reachable page of a German company both are legally required, which is why they are fields rather than a workaround.
Languages: The page can run in several languages; you choose which ones it offers and which is the default.
Visibility of individual parts: Logo, history, affected services and unlinked services can each be shown or hidden.

Two limitations for completeness: prebuilt themes like the ones in the self-hosted edition do not exist in the cloud — styling runs through logo, colours and custom CSS. And the builder for your own page sections starts at the Team plan; logo, colours, favicon and CSS are in every plan.

Who is allowed to see the page?

You decide per page. Public is the default. Alternatively a password protects the page, or access is restricted to a list of email addresses.

Several status pages in one account become the normal case as soon as two audiences need to see different things: a public page with the services every customer uses, and a protected one with the systems only discussed with individual partners. The free plan includes one page, Solo two, Team five and Business fifteen.

Public: Anyone with the address sees the page. The normal case — a status page you have to ask for only does half its job.
Password: One shared password for everyone with access. Suitable for pages that only concern existing customers.
Email list: Access only for the addresses you list. Suitable when contractual partners are known by name and access should stay traceable.

How do customers hear about an incident?

They subscribe to the page. Email, webhook, Slack, Microsoft Teams, Discord and Telegram are available — you decide per status page which of those channels are offered. Subscriptions cover the whole page or individual components.

Email subscribers have to confirm their address before they receive anything. That is not a formality: without it, anyone can enter somebody else’s address, and the first incident notice would be an unsolicited message with your name on it.

Notifications only go out once an incident is published. An automatically detected outage starts as an internal record — automatic publishing is off by default. That is the safety catch that stops a false alarm at three in the morning from reaching every subscriber.

How many subscribers are notified per message depends on the plan: 250 on the free plan, 500 on Solo, 1,000 on Team and 2,500 on Business. More people may sign up — the limit applies to delivery, not registration, and it applies from the oldest sign-ups onward.

What happens on the page during an incident?

An incident moves through four stages: investigating, identified, monitoring, resolved. Every update stays on the page as an entry, so afterwards it is clear when what was known.

Those four stages are the entire vocabulary, deliberately. Adding intermediate stages forces the reader to learn a taxonomy before getting an answer. What matters is in the text of the update anyway.

Planned maintenance runs separately: it is announced in advance, appears as maintenance during the announced window, and closes itself afterwards. Maintenance that reads as an outage costs trust without anything having broken.

What ends up on the page is always a human decision. Detection reports; publishing is a separate step — and one you can deliberately skip when a short blip reached nobody.

Complete status page with overall message, grouped components and 90-day availability bars. — Overall state on top, components below, history as bars — the whole page at a glance.

Does the free plan really stay free?

Yes. The free plan is not a trial and does not expire: one status page, 20 monitored services, checks every two minutes from two locations, 250 notified subscribers per message, 30 days of history, custom domain included. No credit card, no notice period, because there is nothing to cancel.

It gets tight in four places, none of which affects a small setup: more than one status page, more than 20 monitored services, a check interval below two minutes, or more than 250 subscribers who should receive a message. Two things are absent from the free plan entirely: additional team members and API access.

Upgrading is possible at any time and takes effect immediately. Nothing is set up again, no page is moved, no address changes — the limits change, not the installation. Paid plans on the monthly model can be cancelled monthly.

The reverse holds too: if the smaller plan turns out to be enough, you go back. The only reason this page describes the free plan in such detail is that it genuinely is enough for most status pages.

What LIVCK is not the right tool for

A status page answers one question very well and several others not at all. For these four jobs, something else is responsible:

Individual customer cases

The page reports states, not transactions. Someone who wants to know why their specific invoice never arrived needs support, not a green component.

A picture of your architecture

Components describe what customers use, not how it is built. Publishing your system landscape explains nothing and exposes plenty.

Waking your own team

Subscribers are your customers. Reaching people internally needs alerting with escalation and on-call. Both live in the same account, but they are a different path.

Prebuilt themes

The cloud has no theme picker. Styling runs through logo, primary and secondary colour, and custom CSS.

These four are stated here so the decision happens before the account, not after it.

How to set it up

Five steps, roughly a minute each. None of them is irreversible.

Create the account
Enter an email address, confirm it, name the organisation. No credit card, no trial that runs out.
Put the first service under monitoring
Choose the HTTP/HTTPS check type and enter the URL — the first run needs nothing more. To maintain a state by hand instead, choose the check type “Manual”.
Create the status page
Enter a name and a slug. That makes the page publicly reachable at yourcompany.statuspage.de, with no further step.
Arrange the components
Assign services as components, sort them into groups and name them in your customers’ language. This step decides whether the page gets read or closed.
Branding and custom domain
Upload logos for light and dark, set the colours, link imprint and privacy policy. Then add the CNAME and TXT records — once both are correct, the page runs on your address.

Which plan limits matter here

Five limits matter for running a status page. Everything else in a plan concerns monitoring, not the page.

Limit	Free free	Solo €19 / month	Team €49 / month	Business €119 / month
Status pages More than one is needed when two audiences should see different things.	1	2	5	15
Monitored services Every component takes its state from a service.	20	50	150	400
Notified subscribers Per message. More may sign up — the limit applies to delivery.	250	500	1,000	2,500
Custom domain The certificate is issued and renewed automatically.	included	included	included	included
History on the page How far the availability bars reach back.	30 days	90 days	180 days	365 days

Prices are net, plus 19 % German VAT. LIVCK is a business-to-business offering.

All plans in detail

Frequently asked questions

What does a status page cost with LIVCK?

On the free plan, nothing, permanently — one status page, 20 monitored services, 250 notified subscribers per message and a custom domain are included, with no credit card. Above it are Solo at 19 euros, Team at 49 and Business at 119 euros net per month.

How long does it take to create a status page?

About five minutes to a publicly reachable page: account, first service, status page, components, branding. Adding a custom domain means waiting for two DNS records to propagate.

Do I need a custom domain?

No. Every status page is immediately reachable at its own address on statuspage.de. A custom domain can be added at any time and is included in every plan, including the free one.

Does my status page run on my own infrastructure?

No, and that is the point. A status page hosted on the same servers as the monitored services is gone exactly when it is needed. The cloud edition runs separately, on servers in Germany.

Can I make the page non-public?

Yes. Per page you can choose between public, password-protected, and a list of permitted email addresses. The common setup is both: a public page for all customers, a protected one for individual partners.

How many subscribers can I notify?

On the free plan 250 per message, then 500, 1,000 and 2,500. More people may sign up — the limit applies to delivery, not registration, and it applies from the oldest sign-ups onward. Email subscribers must confirm their address first.

Can I maintain states by hand, without monitoring?

Yes, using the “Manual” check type. No automatic check runs, and the state only changes when a human changes it. Useful for anything that cannot be measured from the outside.

Can I switch plans or stop later?

Upgrading takes effect immediately and sets nothing up again — address, components and subscribers stay. Paid plans on the monthly model can be cancelled monthly, and the way back to the free plan stays open.

Still comparing?

LIVCK vs Atlassian Statuspage LIVCK vs Better Stack LIVCK vs Uptime Kuma

Your status page is five minutes away

Free account, one status page, 20 services, custom domain. No credit card, no expiry date.

Try LIVCK Cloud for free Install self-hosted

Everything on this page reflects the feature set of LIVCK Cloud as of 26 August 2026. Plan limits can change — the pricing page is authoritative.