A public status page connected to the checks behind it
MOJAQ combines public status pages and uptime monitoring with errors, logs and deploys, keeping the operational record in Helsinki under an included DPA.
EU-hosted in Helsinki · GDPR-native · free during the private beta, no fixed end date
MOJAQ vs Atlassian Statuspage
| MOJAQ | Atlassian Statuspage | |
|---|---|---|
| Public service status | Included | Established status communication |
| Uptime monitoring | Included in the same suite | Integration and plan dependent |
| Incident context | Errors, logs and deploys nearby | Communication-focused workflow |
| Best fit | Compact developer operations | Broader stakeholder programmes |
| Data residency | Helsinki, Finland | Depends on service arrangement |
| DPA | Included | Available terms |
| Access now | Free during the private beta | Free and paid plans |
The public page and the private signal
A status page serves customers; an uptime check serves the responder. They should describe the same service without exposing the same level of detail. MOJAQ keeps both workflows in one suite: endpoint and port checks establish operational state, while a public page presents customer-facing service health without exposing raw diagnostics.
That shared foundation reduces a common failure mode in which the polished public page lags behind what engineers already know. It does not remove judgement about which checks should be public. A degraded internal dependency may not affect customers, while a partial product failure may deserve wider communication even if a broad homepage check remains green.
Build a page for decisions, not decoration
Start with a short list of customer-recognisable capabilities: API, dashboard, uploads or notifications are more useful than internal hostnames. Define which monitor represents each public capability, who owns that mapping and what other communication process your team uses during an outage. A sparse, current page creates more trust than a long component catalogue nobody maintains.
MOJAQ puts errors, logs and deploy tracking next to uptime state. Those private signals help the responder establish scope and sequence before any wider customer communication. The cross-tool timeline can show whether a release preceded the availability change. Customers still receive concise public service health rather than raw diagnostic detail.
When a dedicated communication platform wins
Atlassian Statuspage is built for mature status communication programmes. If your organisation relies on advanced stakeholder workflows, a large subscriber operation or specific enterprise integrations, validate those needs carefully; a dedicated platform may remain the right choice. MOJAQ's fit is a smaller technical team that wants public status tied closely to everyday monitoring in one account.
Service names, incident history and operational timestamps can reveal infrastructure patterns, even when a page is publicly readable. MOJAQ hosts its private service data in Helsinki and includes a GDPR DPA. The same EU residency covers the error, log, deploy and uptime context behind the public update, giving procurement one coherent processing story.
How to move a public status page
Map existing components to customer-facing capabilities before copying them. Recreate the page in MOJAQ, connect the relevant uptime checks, then use a controlled test failure and recovery to verify that public service health follows the intended monitor. Review the page on mobile and share its new URL internally before changing any public link. Export incident history or subscriber information you are required to retain; do not assume a public page migration also transfers every communication workflow.
Questions
Does MOJAQ include both monitoring and a public status page?
Yes. MOJAQ includes uptime monitoring and public status pages in the same suite, with errors, logs and deploy context available to responders.
Is MOJAQ identical to Atlassian Statuspage?
No. Atlassian Statuspage is a mature, dedicated communication platform. MOJAQ is aimed at teams that want a public page closely connected to a compact monitoring and developer toolchain.
What information should a public component show?
Use names customers recognise and publish only the detail they need to make decisions. Keep internal hostnames, raw logs and sensitive diagnostic context out of the public page.
Where is the underlying operational data hosted?
MOJAQ hosts service data in Helsinki, Finland, under an included GDPR DPA.
Publish service health from the monitoring workflow
Give customers a clear status page while responders keep errors, logs and deploy context in one EU-hosted suite.
Request beta access →