Provider clusterLifecycleUpdated 2026-11-06

Kamatera billing, backup, cancel: export and restore before you terminate

Power-off is not free. Snapshots are not app exports. Prove the final copy, then terminate—and Disable Account only when nothing billable remains.

Workload before headline price — verify the plan, terms and recovery path
How to use this. Steps reflect common operator problem-handling patterns and public Kamatera flows. Follow your live console labels; discover actual OS, services, and paths on your host before production changes.

Build a live cost ledger

Start from the calculator, but label display estimates (including ÷730 hourly) as non-invoice.

FieldRecord
ModeMonthly or hourly
ShapeType, vCPU, RAM, disk, DC
TrafficPackage + Asia 1 TB / unmetered conflicts to verify
Add-onsExtended daily, Managed (~$50 seed), licenses
TrialStart date, $100/1 server/1 TB, terminate-before-end
Type A ratesFAQ $0.00054/hr vs calculator/730 — both labeled

Monthly vs hourly lifecycle

  • Monthly: prepaid; FAQ emphasizes terminate before the 1st; cancel after the 1st still pays the current month; TOS: no refund for current prepaid month.
  • Hourly: post-billed; terminate stops further usage charges; expect an invoice the following month for prior usage.
  • Power-off: residual storage + IP—not a free pause.
  • Disable Account: only with no active servers and no debt, via User Profile → Account Status.
  • Suspension: failed card, insufficient deposit, or suspected fraud—update payment/deposit; no evasion tips.

Backup matrix — Extended daily, snapshots, images, exports

MechanismProtectsPrice evidenceNot sufficient when
Extended daily backupDaily external copies; ~14 daysStorage-linked fee; calculator ≈ 0.5× storage lineNot free default; confirm restore process
SnapshotsPoint-in-time Revert/CommitList price UNKNOWN in capturesNot app-consistent alone
Images / clonesRebuild / migrateBilling beyond products above UNKNOWNNot a substitute for DB dumps
App exportsn8n JSON+DB, WP files+DB, keys, model listsMandatory before terminateSkipping export because snapshot exists

Quiesce/cutoff → export → independent off-host copy → isolated restore proof → only then terminate.

CONTROL WRITES → FINAL EXPORT → VERIFY FINAL-CUTOFF RESTORE → TERMINATE → AUDIT

  1. Inventory all servers, disks, backups, IPs, managed add-ons, licenses.
  2. Freeze writers / define cutoff; take application-consistent exports; verify restore on a non-production target matching that cutoff.
  3. Terminate every billable server/add-on; confirm power-off leftovers are intentional or terminated.
  4. If leaving entirely: zero debt → Disable My Account; attribute vendor GDPR retention notes.
  5. Audit final invoice expectation (especially hourly lag), DNS/mail cutover, secret revocation, off-host archive location.

Never destroy before export. Never accept a restore proof older than the final synchronized state.

Refunds, TOS money rules, SLA claims

  • TOS: no refund for current prepaid month; no partial refund on licenses/add-ons mid-cycle; prices may change—no invented price lock.
  • Idle deposit: 2%/month after 6 months unused; deleted after 30 months (TOS)—attribute vendor text.
  • SLA: 99.9% defined as up to 8 hours unavailability per service year; credit = one month of the failed service (cap US$5,000, once per 12 months); claim within 14 days; many exclusions. Not an AiXVPS performance guarantee.
  • Dedicated refund FAQ was not captured (soft-404)—do not invent money-back windows beyond TOS/trial language.

Fit checks before you pay another month

Still need this DC/size/mode? Compare resize vs terminate+rebuild using live console rules (including any disk decrease limits). Recompose via the review; stand up a new host via setup; migrate apps with exports from n8n / AI.