NodePier may work to keep services available, but guarantees no amount of uptime, offers no service credits, and must not be the only copy of important data.
1. No service-level agreement
NodePier does not guarantee any uptime percentage or continuous availability. There is no contractual uptime target, maintenance-window limit, recovery-time objective, recovery-point objective, support response time, resolution time, or service-credit remedy.
Any availability percentage, health indicator, response estimate, historical measurement, “operational” label, or informal statement is informational only. It does not create a warranty, SLA, or future commitment.
2. Best-effort operation
NodePier may use reasonable operational efforts to keep core hosting and control functions working, investigate failures, restore service, and protect infrastructure. Those efforts are not guaranteed and may be limited by staffing, cost, risk, available information, or third-party constraints.
NodePier may prioritize platform safety and containment over availability. A site or application may be stopped while an incident, vulnerability, abusive workload, or legal issue is evaluated.
3. Planned and unplanned interruptions
Service may be slow, degraded, unavailable, changed, or permanently discontinued at any time, with or without advance notice. Causes may include:
- planned maintenance, updates, migrations, certificate work, or capacity changes;
- software defects, hardware failure, storage failure, operator error, or corrupted data;
- denial-of-service attacks, malicious traffic, security incidents, or emergency containment;
- resource exhaustion caused by a hosted workload or another service;
- power, network, datacenter, VPS, DNS, registry, certificate-authority, or upstream-provider failures;
- government action, legal process, sanctions, labor events, disasters, or other events outside reasonable control; or
- suspension or termination under the Terms or AUP.
Maintenance may occur without a published window when NodePier considers prompt action safer or more practical.
4. Third-party and internet dependencies
NodePier depends on services it does not control, including the VPS network, public internet routing, domain registries and registrars, DNS resolvers, certificate authorities, software repositories, container build inputs, and the Tor network. NodePier is not responsible for their performance or continued availability.
DNS propagation and certificate issuance can be delayed or refused. Onion reachability depends on Tor clients and the Tor network. A healthy NodePier service does not mean every visitor can reach a hosted site from every network.
5. Customer continuity responsibilities
You are responsible for designing around the absence of an SLA. At minimum, you should:
- keep current, tested, independent backups of source code, static content, configuration, databases, uploaded files, secrets, and persistent application data;
- keep domain registration, DNS access, and recovery information under your control;
- protect the only authorized owner private key and optional authenticator recovery material;
- monitor your own sites and applications if availability matters to you;
- design applications to tolerate restarts, rebuilds, changed IPs, expired sessions, and transient dependency failures; and
- maintain an alternate provider or recovery plan when interruption would cause material harm.
NodePier does not create backups of customer content or persistent application data. Deployment releases, container images, metrics, and logs are operational artifacts and must not be treated as a backup or recovery mechanism.
6. Support and incident communication
Support and incident communication are provided on a best-effort basis. NodePier does not promise that a report will be acknowledged, investigated, or resolved within any particular period.
Status messages may be incomplete, delayed, corrected, or omitted during an incident. Estimates are not guarantees. Security details may be withheld when disclosure would increase risk, affect another person, or interfere with an investigation.
Operational contact: contact@nodepier.com
7. Policy changes and separate agreements
NodePier may update this policy prospectively by changing its version and effective date. A separate uptime commitment exists only if it is written in a document that expressly identifies itself as an SLA and is signed by the NodePier operator. Marketing language, interface labels, support messages, and this policy are not an SLA.
If this policy conflicts with the Terms of Service, the Terms control unless a signed SLA expressly overrides both.