Now live vizsu Uptime and vizsu Community are open to everyone

Run your business on one workspace.

A suite of business apps built as one product. Monitoring and community are live today. CRM, email, and email marketing are next.

Free plan included. No card needed.

Everything below is live today

Checks every 30 secondsAlerts by voice callProbes on every continentPublic status pagesIncident timelinesOn-call rotations Forums, Q&A, and groupsModeration built inYour domain, your brandingMember badges and analyticsOne admin consoleSMS, email, and Slack alerts Checks every 30 secondsAlerts by voice callProbes on every continentPublic status pagesIncident timelinesOn-call rotations Forums, Q&A, and groupsModeration built inYour domain, your brandingMember badges and analyticsOne admin consoleSMS, email, and Slack alerts
〉 The suite [1/8]

Every app joins the same workspace.

Live apps ship complete. Coming apps arrive in the same console, with your team, permissions, and billing already set.

〉 Live today [2/8]

Two apps in production.

Not betas, not waitlists. Two production apps you can put real traffic and real users on today.

Point tools

The stack you assemble.

  • Separate vendors for monitoring, community, CRM, and email
  • A login, an invoice, and an admin panel for each
  • Integrations that are your job to maintain
vizsu

The stack that arrives assembled.

  • One login, one bill, one admin console — across every app
  • Enable a new app and your team is already in it
  • Data that stays in one place and exports from one place
〉 How it works [3/8]

Adding an app is a toggle, not a project.

Your workspace already knows your team, your domain, and your billing. New apps inherit all of it.

〉 admin console
$ vizsu apps --status

● uptime       live · checks every 30s
● community    live · forums, q&a, groups
○ crm            coming soon
○ email          coming soon
○ campaigns      coming soon

$ vizsu uptime add https://api.example.com
 monitor created · first check in 30s
01 / CREATE

Create a workspace.

Sign up once. The workspace holds every app, user, and setting.

02 / TURN ON

Turn on an app.

Enable Uptime or Community from the console. No separate signup.

03 / INVITE

Invite your team.

Add people once. Roles and access carry across every app.

04 / ADD MORE

Add apps as they ship.

CRM, email, and email marketing land in the same workspace. No migration, no new vendor.

05 / RUN

Run it from one console.

Users, billing, and security for the whole suite, in one place.

〉 Reliability [4/8]

The part of your stack that watches the rest.

A monitoring product has two jobs: notice failure and say so fast. Every design decision in vizsu Uptime serves those two jobs.

Checks from every continent

Each monitor is probed from multiple regions, so one network's bad day doesn't read as your outage.

Alerts that escalate

SMS, voice call, email, and Slack. If a page goes unanswered, the on-call rotation decides who hears about it next.

~10s ~20s ~45s Push SMS Email
Status pages

Public by design

A hosted, public status page your customers can check before they email you.

Incidents

Timelines, not guesswork

Every incident gets a record: when it started, who was paged, when it resolved.

On-call

Rotations built in

Schedule who gets paged and when. No third-party paging tool required.

Channels

Four ways to reach you

SMS, voice call, email, and Slack — pick what fits each monitor.

See full FAQ →

〉 Teams [5/8]

Made for the people who run things.

Engineering

On-call without another vendor.

Monitoring, paging, and status pages in one place, beside the rest of your tools.

Community

A home for your users.

Forums and Q&A under your brand, with moderation and analytics you don't have to assemble.

Founders

A stack that starts consolidated.

Begin with two apps. Add CRM, email, and campaigns as they ship — no migration later.

IT

One surface to administer.

Users, permissions, and billing for every app, managed from a single admin console.

〉 Administration [6/8]

The boring parts, done properly.

We're a young company, so we don't lead with badges. We lead with the controls themselves — and straight answers about where we are.

Console

One console for every app.

Manage members, roles, and billing across the suite from a single place.

Access

Permissions follow the workspace.

Grant someone access once. Every app respects it, including the ones that haven't shipped yet.

Billing

One invoice.

Every app on one bill. Finance reconciles a single line item, not five vendors.

Security

Practices over badges.

Encryption in transit and at rest, least-privilege access internally, reviewed changes. We're early on formal certifications and say so plainly — ask us specifics and you'll get specifics.

Privacy

No lock-in.

Self-serve export and account deletion, no retention games. Leaving vizsu should take an afternoon, not a procurement cycle.

〉 From the team [7/8]

Too new for testimonials. Here's how we work instead.

"We'd rather earn a testimonial than write one."

vizsu is new, so this space holds our operating principles instead of borrowed praise. When customers say something worth quoting, you'll read it here.

The vizsu team · Operating principles
"An alert at 3am should deserve the wake-up. We tune for signal, not noise."
Founding engineer · vizsu Uptime
"Your community is yours: your domain, your members, your data. That stays true if you ever leave."
Founding engineer · vizsu Community
〉 Questions [8/8]

Asked by people who read the fine print.

01What is actually live today?+

Two apps: vizsu Uptime, for website, API, and server monitoring, and vizsu Community, for branded forums, Q&A, and groups. Anything marked coming soon is not live yet, and we won't pretend otherwise.

02When do CRM, Email, and Email Marketing ship?+

They're in active development, in that order. We don't publish dates we might miss; when a date is firm it will be on this page, and existing customers hear first.

03Can I use just one app?+

Yes. Every app works on its own. The suite is a convenience, not a requirement — start with Uptime or Community alone and add the rest only if they earn it.

04Who owns my data, and can I export it?+

You do. Every app has full export — monitors, incident history, community posts, members — in open formats like CSV and JSON. Leaving should be a decision, not a project.

05What is your security posture?+

Data is encrypted in transit and at rest, and internal access is role-limited and logged. We're a young company: we don't hold certifications yet and won't claim ones we don't have. Audits are planned — ask us where they stand.

06What does one workspace actually mean?+

One account, one member directory, one admin console, one bill. When you enable a new app, your team, permissions, and billing are already there.

07What are the free plan's limits?+

The free plan is a working tier, not a trial — enough to monitor a small site or run a small community indefinitely. Exact per-app limits are shown at signup, and we won't quietly shrink them.

Start with what's live. The rest arrives on its own.

Create your workspace
0
Uptime checks run to date