System status
This page does not show live monitoring
Novus does not yet run an automated uptime monitor, so there is no probe behind this page and it will not tell you whether a service is up right now. Rather than print a green tick nobody measured, it tells you something more useful during an incident: which parts of Novus can be affected at all. Most of the product runs on your machine and keeps working regardless.
What depends on what
Visualizer rendering and preview
Runs in your browserRuns on your GPU via the browser canvas. Once the editor has loaded, a Novus server incident cannot stop a render.
Audio analysis and beat detection
Runs in your browserWaveform, frequency-band and beat-grid analysis all execute in the browser on the file you selected. Your audio is never uploaded to run them.
Video and audio export
Runs in your browserEncoding happens locally. There is no render queue, so exports cannot back up behind other users and are unaffected by server load.
Marketing, help, tutorial and blog pages
Needs Novus serversStatically prerendered and served from the edge CDN. These stay up through a database outage because they never touch the database.
Previously visited pages, offline
Runs in your browserA service worker caches pages you have already opened and falls back to a dedicated offline page, so a dropped connection is not a dead end.
Sign-in and accounts
Needs Novus serversRequires the auth service and the database. If these are unavailable you can still edit and export as a guest; you just cannot save to the cloud.
Cloud project saves and private assets
Needs Novus serversRequires the database and blob storage. Work in progress lives in the browser until you save, so an outage here does not discard the composition on screen.
Community gallery, publishing and remixes
Needs Novus serversRequires the database. Browsing, publishing, reactions and comments are all unavailable during a database incident.
Advertising
Third-partyServed by Google AdSense. An AdSense outage leaves blank slots and affects nothing else on the page.
Upstream providers
When something server-side is broken, these are the three places worth checking before reporting it. A provider incident is the most common cause and they do publish live status.
Vercel
Hosting, edge CDN, serverless functions, blob storage
Turso / libSQL
Accounts, saved projects, community data
Google AdSense
Advertising
If something is broken
- Check whether the affected subsystem is marked “Runs in your browser” above. If it is, the cause is local: try a hard reload, a different browser, or a smaller audio file.
- Check the three provider status pages.
- Still broken? Report it with the page URL, what you were doing, your browser and OS, and anything in the browser console. Email visualizers@novusstreamsolutions.com or use the contact page.
Related: Changelog · Accessibility · Help Centre