Cloud Infrastructure Pricing Policy

This policy defines pricing, metering, cloud-provider selection, data/compliance posture, SLA coverage, and migration for all Tanqory cloud infrastructure customers. It is drafted to be operational and platform-grade for global use.

1) Introduction and scope

Applies to all Tanqory cloud infrastructure services (compute, storage, network, managed services) across Standard and Enterprise plans.
Forms part of the Terms, Billing Policy, Acceptable Use Policy, and any contract/Order Form. If conflicts arise, the stricter/more specific document prevails.
Covers pricing, quotas, overage, provider choice, migration, invoicing, and cloud-specific SLA.
Applies to all supported regions/providers, including tax and FX handling per the Billing Policy.
Use of services after the effective date constitutes acceptance; if you do not agree, cancel before the effective date.
Customers must keep billing/tax/contact information accurate and up to date.
Reference currency is USD; other currencies use mid-market FX at billing time (see Billing Policy).
Contract/industry/country-specific annexes may override conflicting general text.
Tanqory may update this policy to meet legal/partner requirements and will give advance notice of material changes.
Billing, payment, refunds, and disputes follow the Billing Policy.

2) Key definitions

“Cloud Provider” means the external infrastructure provider Tanqory contracts with (e.g., DigitalOcean, AWS, GCP, Azure, Linode/Akamai).
“Cloud Plan” means the bundle of resources/features/quotas and pricing (e.g., Standard/Pro/Business/Enterprise) shown on the packages page/Order Form.
“Compute resources” are vCPU/RAM allocated per instance or container by chosen size.
“Storage” includes block/object/db storage measured in GB/TB per month, rounded to the stated minimum unit.
“Bandwidth (Data Transfer)” is inbound/outbound measured in GB/TB per month, rounded to the stated minimum unit.
“Overage” is usage beyond plan quotas, billed at the published rate.
“Premium uplift” is an added fee for premium providers/regions or higher-cost add-ons.
“SLA” means Tanqory’s service level commitment for uptime/response that is credit-eligible.
“Business Day” means Monday–Friday excluding Singapore public holidays, unless otherwise stated.
Other definitions follow the Terms/Order Form or Billing Policy; if inconsistent, the more specific document prevails.

3) Supported providers and pricing tiers

Standard Providers (included in base price): DigitalOcean, Linode/Akamai—suitable for general workloads; no uplift.
Premium Providers (with uplift): AWS, GCP, Azure—uplift per resource/region as shown in the dashboard/Order Form.
Provider/region choice depends on compliance/latency/integration needs.
Multi-provider per project is allowed where permitted by contract; uplift applies per provider/region used.
Tanqory manages cloud contracts/licenses and passes through negotiated pricing (plus uplift, if any) transparently.
Upgrading from Standard to Premium requires price confirmation before the next billing cycle unless the customer agrees to immediate effect.
Enterprise customers may specify one or multiple providers with spend caps in the Order Form, if stated.
Migration between supported providers is available; fees per Section 9 and uplift of the new provider apply.
Provider certifications (e.g., SOC/ISO/FedRAMP) are published in security documentation; evidence available via enterprise@tanqory.com.
If law/sanctions restrict certain providers/regions, Tanqory may deny or limit selection to comply.

4) Pricing structure, base rates, and uplift

Base price includes compute/storage/network for Standard Providers per package sizes shown in the dashboard/pricing page.
Premium uplift is a percentage or fixed rate per unit (vCPU/GB storage/TB egress) by provider/region.
Prices are in USD; other currencies use mid-market FX at billing time without markup (bank FX fees are customer’s responsibility).
Prices exclude tax unless stated “tax-inclusive”; VAT/GST/Sales Tax follow the Billing Policy and local law.
Add-ons (backup, snapshot, managed DB, CDN, WAF) may have specific rates and usage-based or per-instance charges.
Egress quotas/caps are clearly published; overages follow Section 5.
Enterprise customers may negotiate volume/commit discounts via Order Form; over-commit usage may be on-demand rates.
Price/uplift increases that add customer cost will be announced ≥30 days in advance unless driven by tax/mandatory law.
If provider costs increase as pass-through (e.g., global egress hike), Tanqory will notify and offer options to switch provider/region.
Current plan examples and rates are in the dashboard/pricing docs; if a contract states specific rates, those govern.

5) Metering, rounding, and overage

Usage measured in UTC; rounding per documentation (e.g., vCPU-hours round up minimum 1 minute/hour; storage rounds to GB per month).
Compute overage billed on excess vCPU-hours/RAM-hours; storage overage on average monthly GB beyond quota; bandwidth overage on egress beyond cap.
Overage rates are published in the dashboard and Order Form and may vary by provider/region.
Quota alerts (e.g., 80%/90%/100%) via dashboard/email; customers should set notifications for relevant roles.
If anomalous usage is detected, Tanqory may throttle/suspend to protect systems/costs and will provide reasons.
True-up occurs at billing cycle end using usage logs; if incomplete, reasonable estimates will be used and disclosed.
Historical usage available in the dashboard for at least 12 months, or longer per Enterprise contracts.
CSV/JSON reports for reconciliation/tax available via support or account manager.
If soft caps/auto-shutoff at quota are needed, configure in dashboard or request support.
Rounding/metering is not used to hide costs and aligns with common PSP/cloud practices.

6) Data center regions, data residency, and compliance

Customers choose supported regions (e.g., SG, US, EU) for latency/compliance needs.
Customer data is typically stored in the chosen region; some logs/backups may be replicated cross-region for durability (disclosed in service docs).
Cross-border transfers use legally valid mechanisms (e.g., SCCs/IDTA/adequacy) plus technical/organizational measures (encryption, least privilege, access logging).
Customers must assess sectoral data requirements (e.g., health/finance/government) before selecting provider/region.
Supported providers carry certifications such as SOC 2/ISO 27001/PCI DSS; workloads needing FedRAMP/HIPAA/government use only compatible services.
If law/sanctions bar a region/provider, Tanqory will deny or migrate workloads as required.
Enterprise customers may request a DPA and third-party vendor (TPV) details for DPIA/LIAs.
Shared responsibility: Tanqory handles platform/base configuration; customers handle apps/data/system-specific settings.
Backups/DR follow published schedules and may use same/adjacent regions per business continuity policy.
Compliance evidence requests go through enterprise@tanqory.com and may require an NDA.

7) SLA and service credits

Monthly uptime targets: Standard Providers ≥99.9%; Premium Providers (AWS/GCP/Azure) ≥99.95% or higher per chosen service.
Sample credits (of infra fees for that cycle): 99–99.9% = 10%; 95–99% = 25%; <95% = 50% (or higher if contract states).
Credits are non-cash, applied to next invoice; claims due within 30 days of event with evidence of outage time and impact.
Credits excluded for exceptions (e.g., scheduled maintenance with notice, customer code/config faults, force majeure, blocks due to AUP/law violations).
SLA covers only Tanqory-managed layers (orchestrator/network overlay/provider management), not customer applications.
Multi-provider/region setups may have separate SLA per service or Enterprise contract.
Uptime measured by Tanqory monitoring and provider logs; contract’s dispute-resolution source of truth applies if conflict.
Add-ons (managed DB/CDN/WAF) may have specific SLA/credits in service docs/Order Form.
Total credits per cycle capped at the infra fees for that cycle unless Enterprise contract allows more.
During serious security events, Tanqory may temporarily reduce SLA to protect systems, with notice.

8) Security, standards, and testing

Tanqory uses providers with security certifications (e.g., SOC 2, ISO 27001, PCI DSS) and enforces encryption in transit/at rest.
Least privilege is applied for cloud access; critical actions are audit-logged.
Customers must enable MFA and safeguard keys/tokens.
Pentest/vulnerability scans on Tanqory environments require prior written approval with defined scope/time.
Do not use the service to attack/scan third parties or bypass platform security.
Workloads involving card/health/sensitive data must use compliant services/configurations (e.g., PCI scope isolation, HIPAA-ready components).
Tanqory patches the layers it manages and will notify if significant downtime impact occurs.
If security incidents affect data, customers must notify per data-protection law; Tanqory will cooperate on assessment/notification.
Logging/backup follow published cycles; access is role-restricted.
Shared responsibility boundaries are documented in runbooks/security docs.

9) Migration/provider change and costs

Migration to/from supported providers is offered with risk/downtime/cost assessment in advance.
Migration fees may include engineering effort, temporary double-run, temporary storage/egress, and cutover services.
Customers must provide team/decision-makers for freeze/change windows and pre-cutover testing.
Standard playbooks exist for lift-and-shift, replatform, or multi-cloud migrations; chosen per suitability.
Complex migrations (multi-region/data-sovereignty) may need a separate SOW and specific SLA.
Tanqory will propose cost-reduction options (e.g., off-peak snapshot/rsync, egress minimization) where feasible.
Customers must pay migration quotes/SOW and any overage/egress incurred during migration.
Double-run may create overlapping costs; Tanqory will estimate before starting.
After cutover, legacy resources will be deprovisioned per plan and data deleted per retention policy/customer instruction.
Submit migration requests to enterprise@tanqory.com with system details/timeline/regions/regulatory notes.

10) Billing, tax, and disputes

Billing/payment/tax/refunds follow the Billing and Payment Policy; this policy sets rates/quotas/overage inputs.
Invoices are monthly (UTC) or per Enterprise contract; line items show base/overage/uplift/tax transparently.
Delinquency may trigger suspension/reserve/hold per Billing Policy and contract.
Dispute charges within 30 days of invoice date with usage/log evidence; Tanqory targets responses per Billing Policy Annex B SLA.
Provider/region/add-on changes mid-cycle may prorate or create temporary charges.
Tax/invoicing use customer-provided tax data; if incomplete, full statutory tax may apply.
FX/bank fees are the customer’s responsibility unless a contract states otherwise.
Enterprise plans may set spend caps/alerts and request detailed spend reports.
Contracted SLA credits, if any, are in the Order Form/annex and offset next cycle.
Primary dispute/appeal channels: billing@tanqory.com and support@tanqory.com within stated timelines.

11) Price/quota/provider changes

Price/uplift increases that add customer cost: ≥30 days’ notice (email/dashboard) with effective date.
Adding/removing supported providers/regions: announcement plus reasonable migration/plan-change options.
Quota cap or overage-rate changes under contract: coordinated with Enterprise customers via account managers.
If law/sanctions force closure of regions, Tanqory will propose migration/credits as reasonable.
Feature/add-on changes impacting cost will state impact in notices and update dashboard pricing.
Customers may terminate before effective date if rejecting new prices, per Billing Policy/Terms.
Expired discounts/promos revert to standard pricing unless renewed.
Order Forms with fixed/commit rates remain until contract end unless adjustment rights are stated.
Changes take effect on the new cycle unless the customer consents to immediate effect (documented via email/dashboard).
Change notices posted at https://legal.tanqory.com/ and/or in the dashboard.

12) Contact channels

General/sales: sales@tanqory.com
Pricing/billing/tax: billing@tanqory.com
Technical support: support@tanqory.com
Enterprise/commercial/compliance docs: enterprise@tanqory.com
Policy site: https://legal.tanqory.com/
Security/AUP violations: abuse@tanqory.com (see AUP/Security Policy)
Emergency (Enterprise): as stated in Order Form/Runbook
Include account/invoice/project IDs when contacting to expedite responses.
Policy/price updates will appear in the dashboard and registered-email notices.
Records of key communications are retained for audit/legal compliance.

13) Appendix A: Sample pricing/overage/uplift (refer to live Pricing for binding numbers)

• Figures here are illustrative; binding rates/limits are in the live dashboard/Pricing page and/or latest Order Form (https://tanqory.com/plans-pricing or dashboard pricing).
• Reference Standard Provider pricing (DigitalOcean/Linode) SG/US/EU example: vCPU $12/mo, RAM $6/GB/mo, block storage $0.10/GB/mo, egress included up to 2 TB/mo; egress overage $0.09/GB.
• Premium uplift (example): AWS/GCP/Azure +30–60% per vCPU/GB storage/TB egress by region (see current numbers in dashboard/Order Form).
• Base egress cap: 2 TB/mo included for Standard; Premium caps per provider; beyond cap, overage per published rate.
• Managed DB/Cache uplift: +15–35% over base compute/storage (depends on provider/storage type).
• Backup/Snapshot: $0.02–0.05/GB/mo by storage tier; recovery/restore may incur traffic at egress rates.
• CDN/WAF (if available): starting $0.05/GB (CDN) and $30/node/mo (WAF) or provider-native rates if chosen.
• These figures are general examples; if an Order Form lists specific prices, those govern.