ORDNARY WEB SERVICES
Ordnary Web Services
Last updated November 15, 2026
How Ordnary Web Services works, how we process your data when you use it, and the terms that apply to our cloud platform.
Ordnary Web Services is our European cloud platform for developers: object storage, serverless databases, feature flags, and protection for your own servers, all managed from one console. This page explains what Ordnary Web Services is, how we process your data when you use it, and the terms that apply. It supplements the Terms of Service, the Acceptable Use Policy, the Billing & Refund Policy, and the Service Level Agreement; for business customers, the Data Processing Addendum also applies.
What Ordnary Web Services is
Ordnary Web Services consists of the following products:
- Ordnary R2: S3-compatible object storage, with no egress fees, an optional EU data jurisdiction, and custom domains;
- Ordnary Serverlite: serverless SQLite databases you query over HTTPS;
- Ordnary Halyard: feature flags and remote configuration, currently in beta and free of charge; and
- Ordnary Netway: DDoS protection, a web application firewall, and TLS for a server you run yourself, currently free of charge.
You manage all products from the Ordnary Web Services console at console.cloud.ordnary.com, signed in with your Ordnary Account, or through our API and SDKs as described at docs.ordnary.com. You choose which products you use and how you configure them.
What data we process
In delivering Ordnary Web Services, we process two kinds of data.
Account data: your Ordnary Account and its settings, your billing details, and the API tokens and access keys that have been issued for your resources.
Customer data: the content, code, and data you place on your resources or have processed, such as objects in an Ordnary R2 bucket, rows in an Ordnary Serverlite database, flag configurations in Ordnary Halyard, or traffic that passes through Ordnary Netway. This data remains yours; we only process it to deliver the service and as you instruct under the Data Processing Addendum.
We use account data to determine who has access to which resources, to run your resources as you've configured them, and to bill you for your usage. We don't read or use the contents of your customer data except as necessary to deliver or support the service, for example to detect abuse.
Regions and data residency
Where a product offers a location setting, such as the EU data jurisdiction for an Ordnary R2 bucket, you choose where your data is stored. That choice is an explicit setting you control, not a location we infer about you; see our Location Data page for more on that distinction. When you choose the EU data jurisdiction, the data in that bucket is stored and processed within the European Union. Without such a setting, data may be stored and served from our hosting provider's global network, as described on our Subprocessors page.
Your workloads and responsibility
You're responsible for the resources you create, the software and content you run or store, your configurations, and your end users. You must:
- secure your account, access keys, API tokens, secrets, buckets, and databases;
- keep the software you run, including any server you protect with Ordnary Netway, patched and configured safely;
- comply with the Acceptable Use Policy and the acceptable-use requirements of our underlying infrastructure providers; and
- not use Ordnary Web Services to harm or attack others, host malware, run abusive proxies, send unlawful bulk communications, or conduct prohibited cryptomining.
Accounts and access
You use Ordnary Web Services through your Ordnary Account. You're responsible for keeping your account secure, for managing the API tokens and access keys you create, and for promptly revoking them when they're no longer needed.
Backups and deletion
Backups are your own responsibility, unless a product explicitly includes them. Where backup or recovery features are offered, you remain responsible for verifying and exporting critical data.
When you delete resources or close your account, data may be irreversibly destroyed. Export anything you need before deleting resources or closing your account. We may retain limited records as required by law.
Availability, maintenance, and SLAs
We target a monthly uptime of 99.9% for Ordnary Web Services. If we don't meet that target, you can request service credits as set out in our Service Level Agreement. We may perform planned and emergency maintenance and will give reasonable advance notice for planned maintenance where practicable. Service credits are governed solely by the Service Level Agreement.
Capacity, limits, and fair use
We may set quotas, resource limits, and fair-use thresholds to protect the platform. We may decline, throttle, or suspend resource-intensive or abusive workloads. Some capacity depends on third-party provider availability and is not guaranteed.
Security
We secure the underlying platform with encryption, access controls, network security, logging, and monitoring. Security of Ordnary Web Services is a shared responsibility: we secure the platform, you secure your workloads, data, configurations, and access. See our Security Policy for the full overview.
Subprocessors
Parts of Ordnary Web Services run on third-party infrastructure, such as hosting providers. These parties are bound by obligations no less protective than our own. See our Subprocessors page for the full list.
Billing
Ordnary Web Services is billed postpaid: once a month, in euros, based on what you actually used, as described in the Billing & Refund Policy. There are no subscriptions. Each product has a free monthly allowance, and usage within it costs nothing. Any credits on your account are used first; the remainder is charged to your payment method. Usage above the free allowance requires a valid payment method on file. Stored data accrues charges until you delete it, even if it isn't accessed. You're responsible for monitoring and controlling your own spend.
Suspension and termination
We may suspend or terminate Ordnary Web Services for abuse, security risk, legal requirement, or breach of these terms. We may suspend specific resources to protect the platform. Where practicable, we'll notify you.
If an invoice remains unpaid, we only pause the creation of new resources until it's paid. Your existing resources keep working, and we never delete your data for non-payment.
Third-party infrastructure
Parts of Ordnary Web Services rely on third-party infrastructure. Their outages, policy changes, or restrictions may affect Ordnary Web Services, and their terms may apply to the relevant components. We're not liable for losses outside our reasonable control.
Changes
We may update this page and the terms described here as Ordnary Web Services evolves. We'll communicate material changes as described in the Terms of Service.
Contact
Ordnary Web Services questions: support@ordnary.com. Security: security@ordnary.com.
For urgent requests, call +31 85 401 3197.