Platform availability
Limvero is operated with production release gates, health checks, backups and rollback workflow. Specific uptime commitments or credits apply only when agreed in a signed SLA.
Service Level Agreement.
Availability, incident and service objective boundaries for restaurants using Limvero.
Service objectives
These objectives describe Limvero operational intent. Contractual uptime, response commitments or service credits require a signed customer SLA.
Status communication
Confirmed incidents, maintenance notices and customer-impact summaries are communicated through the public status page or direct account channels.
Data protection operations
Backup, restore and tenant export workflows support continuity, offboarding and recovery. Restore timing depends on incident scope and hosting environment.
Provider boundaries
Payment, fiscal, delivery, SMS, email, hosting and hardware providers can affect service availability and remain governed by their own terms.
Maintenance
Planned maintenance is scheduled to reduce restaurant disruption and is announced through status or account channels when customer impact is expected.
Customer responsibilities
Restaurants remain responsible for local networks, devices, printers, provider accounts, staff access, hardware power and operational readiness.
Incident priority model
Priorities help route production incidents and support requests consistently during restaurant operations.
P1 Critical service outage
Production POS, KDS or core login is unavailable for an active restaurant location with no practical workaround.
P2 Major workflow degradation
Core workflows are degraded, delayed or partially unavailable, but restaurants can continue service with a workaround.
P3 Standard defect or request
A non-critical feature defect, configuration issue, report question or integration issue affects limited users or workflows.
P4 Advisory request
How-to questions, onboarding guidance, commercial questions, feature clarification or roadmap discussions.
This public SLA page does not replace a signed agreement. Enterprise customers can agree custom uptime, response windows, maintenance notice and service-credit terms during procurement.
Plan a clean restaurant rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.