Web application
Portal, public website, and admin surface.
System status
Every Nexvendo service is operating normally. We disclose incidents here transparently as they happen, with the timeline and remediation.
Portal, public website, and admin surface.
Email inbox, SFTP feeds, and HTTPS feeds.
Magic-link sign-in, import notifications, weekly digest.
Stripe checkout, customer portal, webhook processing.
When something goes wrong we publish it here with the timeline and a plain-language root cause. Nothing redacted, nothing buried.
Customer data lives in Frankfurt on Supabase (Postgres + Storage). Distributor credentials are AES-256-GCM encrypted with a master key held outside the database. Tenant isolation is enforced by Postgres Row-Level Security at every table.
We don't run a 24/7 SOC. We do run automated cron monitoring, structured webhook audit, and alerting on failure paths. For critical issues during business hours, you'll usually hear from us before you notice.
GDPR Art. 33 requires breach notification within 72 hours; we commit to faster than that for material incidents. Every disclosed incident here includes a plain-language root cause and what we changed.
Active customers receive incident notifications directly by email. Prospects evaluating Nexvendo who want to monitor reliability can subscribe to the same updates.
Subscribe to status emailsYou will only receive emails when an incident is declared, resolved, or post-mortemed. We do not send marketing through this list.
A note on this page. Right now status is manually maintained — when we know about an issue we update it here. We don't yet run a third-party uptime monitor against our public endpoints. When we do (likely Better Stack or Statuspage), the indicators above become live signals. Until then, treat "all systems operational" as our best-effort awareness, not a 99.99% SLA guarantee.