Status

There is no automated status badge on this page yet, and one that is not wired to real monitoring would be worse than none — it would stay green through an outage, at exactly the moment somebody came here to check.

The honest live check is /api/health, which reports whether the application can reach the database right now. If it answers and says database: ok, the core of the product is up.

• Application. Vercel, single region. Serves the marketing site, the planner and every API route.
• Database and authentication. Supabase (Postgres). Holds every project, task and calendar event, and issues the sessions.
• Payments. Stripe internationally, Razorpay in India. An outage at either stops new subscriptions but not the planner.
• Email. Resend. An outage delays receipts and trial email; nothing is lost.
• Error monitoring. Sentry. Errors are captured here, which is how an incident is usually noticed.

No customer-affecting incidents to report. Polylane has not launched, so this is a statement about how short the history is, not about how reliable the product has proven to be. Every incident that affects a customer will be listed here with what happened, when it was fixed, and what changed as a result.

• No uptime SLA. A solo-run product should not sell one it cannot staff. If you need a contractual guarantee, Polylane is not the right tool yet, and it is better to know that now.
• Your data outlives an outage. The planner keeps its state on your device and syncs when the connection returns, so an outage costs you access rather than work.
• Incidents get written down. Anything that affects customers is posted here, including the ones that were our fault.
• You can always leave with your data.Export is on your account page and needs nobody's permission.

Email support@smatsols.com. Include what you were doing and roughly when — that is usually enough to find it in the logs. Security issues have their own route on the security page.