[{"data":1,"prerenderedAt":87},["ShallowReactive",2],{"trust-availability":3},{"id":4,"title":5,"body":6,"description":75,"draft":76,"extension":77,"intro":78,"meta":79,"navId":80,"navigation":81,"ogImage":82,"path":83,"seo":84,"stem":85,"__hash__":86},"trust\u002Ftrust\u002Favailability.md","Availability",{"type":7,"value":8,"toc":64},"minimark",[9,14,18,22,25,29,32,36,45,49,52,56],[10,11,13],"h2",{"id":12},"cloud-hosting","Cloud hosting",[15,16,17],"p",{},"1410SMS runs entirely on cloud infrastructure rather than on-premise hardware, so capacity can be\nadjusted as a school grows, or as the number of schools on the platform grows, without a physical\nserver becoming a single point of failure for your school's access.",[10,19,21],{"id":20},"high-availability","High availability",[15,23,24],{},"The application is designed to be stateless, meaning any request can be handled by any running instance\nof the service rather than depending on a specific server. That is what makes it possible to run\nseveral instances behind a load balancer as demand grows. Background work (emails, WhatsApp\nmessages, PDF generation, notifications) runs through a queue rather than blocking your request, so a\nslow or failed job never holds up the page you're using.",[10,26,28],{"id":27},"scheduled-maintenance","Scheduled maintenance",[15,30,31],{},"Most updates are deployed without any visible interruption. On the rare occasion we need a maintenance\nwindow that could affect availability, we schedule it for low-traffic hours and notify affected schools\nin advance by email wherever practical.",[10,33,35],{"id":34},"incident-management","Incident management",[15,37,38,39,44],{},"If an incident affects the platform, our priority is restoring service, followed by informing affected\nschools of what happened and what we are doing about it. There is no public real-time status page\nyet. It is on our ",[40,41,43],"a",{"href":42},"\u002Ftrust\u002Fsecurity","roadmap",", and until it exists we email affected schools directly\nabout anything significant.",[10,46,48],{"id":47},"planned-uptime-target","Planned uptime target",[15,50,51],{},"We design and operate the platform to be highly available for day-to-day school use. We don't publish a\nformal uptime percentage as a blanket guarantee on this page, since backing that up meaningfully\nrequires the kind of monitoring history and public status page we are still building towards. Schools\nwith a formal SLA requirement, typically as part of a larger procurement, should contact us to discuss\na specific agreement.",[10,53,55],{"id":54},"maintenance-notification-policy","Maintenance notification policy",[57,58,61],"callout",{"title":59,"tone":60},"Our policy","info",[15,62,63],{},"Maintenance that is not expected to affect availability is not announced in advance. Maintenance that\ncould cause any visible downtime is scheduled outside typical school hours where possible and, wherever\npractical, announced by email ahead of time to give schools fair warning.",{"title":65,"searchDepth":66,"depth":66,"links":67},"",3,[68,70,71,72,73,74],{"id":12,"depth":69,"text":13},2,{"id":20,"depth":69,"text":21},{"id":27,"depth":69,"text":28},{"id":34,"depth":69,"text":35},{"id":47,"depth":69,"text":48},{"id":54,"depth":69,"text":55},"How 1410SMS is hosted for high availability, our approach to scheduled maintenance and incident management, and our uptime target.",false,"md","How 1410SMS is hosted, how we handle planned maintenance, and what to expect if something goes wrong.",{},"availability",true,null,"\u002Ftrust\u002Favailability",{"title":5,"description":75},"trust\u002Favailability","QtQvwNUXNrEK8RNWJBHbivO08IBcKFKETeEhsNMcJYE",1785148429025]