Terms

These Terms form a binding agreement between you - or the organization you represent, if you are signing up on its behalf and are authorized to do so - and the company named in the Legal Notice. By creating an account, using the API, or paying for a plan, you accept them.

If you are contracting on behalf of an organization, "you" means that organization, and you confirm you have the authority to bind it.

CapyDB provides managed PostgreSQL databases. Each project gets its own isolated database cell - a Postgres process with its own storage, credentials, and CPU and memory limits - plus the lifecycle around it: provisioning, direct and pooled connections, preview databases, backups, point-in-time restore, imports, and extension management.

You get a standard connection string and standard tooling. What runs on top of the database, and whether it works, is yours.

The service also includes K/V stores (CapyDB Knight/Valkyrie): managed key-value stores, each in its own isolated cell, reachable over an authenticated REST endpoint and the RESP protocol. A K/V store is available on every plan and may be used with or without the database beside it.

• -Keep your sign-in credentials, database credentials, and API keys confidential; anything done with them is treated as done by you
• -Rotate or revoke a key as soon as you suspect it has been exposed - the dashboard and the CLI both do this without a support ticket
• -Use workspaces and API keys only for systems you control or are authorized to operate
• -Keep the account email reachable; incident, billing, and end-of-life notices go there
• -Workspace owners are responsible for the members they invite and the permissions they grant

Do not use the service to break the law, to attack anyone, or to hurt the platform. Concretely, that means no unlawful, infringing, or deliberately harmful content; no attempts to reach another tenant's data or to escape your cell; no scanning, load-testing, or denial-of-service against infrastructure you do not own; no using a database cell as a proxy, relay, or command-and-control endpoint; and no reselling raw capacity as an undifferentiated database service.

Security research against a project you own is welcome. Tell us what you find - see the Security page.

You may benchmark CapyDB and publish the results, including comparisons against other providers. We ask only that you do it in good faith: measure a project you own, document the method fully enough that someone else could reproduce it - plan, region, Postgres version, client location, workload, and the exact commands - and represent the configuration, results, and cost accurately. We may publish our own measurements in reply. No permission, prior notice, or review is required, and nothing elsewhere in this agreement restricts your right to publish.

Each project runs on a plan. The plan sets the hard limits the platform enforces: project count, preview databases, CPU and memory ceilings, connection counts, and storage. Limits are enforced by the control plane, not by policy - exceeding one is a rejected operation, not an invoice surprise.

Storage beyond the plan allowance is metered and billed as used. Current plans and limits are published on the pricing page, which is the operative statement of what each plan includes.

Parts of the platform ship as early access and are labelled that way. Early-access features may change or be withdrawn, and they carry no availability commitment.

• -Paid plans are billed in advance on a recurring monthly term and renew automatically until cancelled
• -Prices are quoted in US dollars; the dashboard may display a localized format of the same amount, never a converted one
• -Metered usage is billed in arrears alongside the next subscription charge
• -Payments and invoicing are handled by our payments processor, which acts as merchant of record and applies the tax rules of your billing location
• -A failed payment starts a retry and notification sequence before any restriction is applied; we do not delete data over a missed invoice without telling you first
• -Price changes are announced at least 30 days before they take effect on your subscription, and you may cancel before they do

You can cancel a subscription yourself, at any time, in the same medium you used to subscribe: the billing section of the dashboard, in a few clicks, with no phone call, no retention interview, and no email required. Cancellation takes effect at the end of the current billing period, and the plan keeps working until then.

Free trials, where offered, convert to a paid term only after the trial length and price have been disclosed to you, and can be cancelled before conversion by the same route.

Fees already paid are not refunded except where the law requires it or where we failed to provide the service. EU consumers have a statutory 14-day right of withdrawal for digital services; requesting immediate provisioning - which is what creating a database does - means you accept that the right lapses once the service has been fully performed.

Deleting a project destroys its database cell and, on the retention schedule of your plan, its backups. Export first: see Data portability and exit.

You own what you put in your databases. You grant us only the licence needed to host, transmit, back up, and restore it in order to run the service for you.

Where your data includes personal data, you are the controller and we are your processor. The Data Processing Agreement is incorporated into these Terms by reference and applies automatically - you do not need to sign anything for it to be in force.

You are responsible for having a lawful basis for what you store, and for not putting data into the platform that you are not permitted to process.

We aim to keep the platform available continuously and publish live status per region. We do not currently offer a contractual uptime commitment or service credits; if your workload needs one, talk to us before you build on it rather than after.

Routine maintenance is applied without downtime where possible. Postgres minor-version updates are applied as a restart, and a cell that is asleep takes its update on the next wake at no cost to you. Disruptive maintenance is announced in advance, except where a security fix cannot wait.

K/V stores are held in memory with a periodic snapshot. They are not backed up, are not covered by point-in-time recovery, and will evict data once the store reaches its capacity. They are intended for transient state - rate-limit counters, sessions, caches and locks - and you should not use one as the system of record for anything you cannot reconstruct.

We may suspend a project or an account for non-payment after notice, for a breach of the acceptable-use rules, or where continued operation threatens the platform or another tenant. Where the situation allows it, we warn first and give you a chance to fix it.

You may terminate at any time by cancelling and deleting your projects. On termination for any reason we delete your cells and let their backups age out; you are responsible for exporting anything you want to keep before you go.

The platform, its software, and its brand remain ours. Nothing here transfers ownership of either side's intellectual property. Our open-source components are governed by their own licences.

If you send us feedback or a feature request, we may use it without obligation or compensation. This does not give us any rights in your data or in your own products.

CapyDB K/V is powered by Valkey. Redis is a registered trademark of Redis Ltd. and Valkey is a trademark of LF Projects, LLC. Any use of those marks is referential: it describes protocol and client compatibility, and implies no affiliation with, sponsorship by, or endorsement from either organisation.

We provide the service with reasonable skill and care, and we operate it the way the documentation says we do. Beyond that, and to the maximum extent the law allows, the service is provided as-is: we do not warrant that it will be uninterrupted, error-free, or fit for a particular purpose.

Nothing in these Terms excludes liability that cannot lawfully be excluded, and mandatory consumer rights under Greek and EU law are unaffected.

Neither party is liable for indirect, incidental, special, or consequential loss, or for lost profits, revenue, goodwill, or anticipated savings, however caused.

Our total aggregate liability arising out of or in connection with the service is limited to the amounts you paid us for the service in the twelve months preceding the event giving rise to the claim.

These limits do not apply to death or personal injury caused by negligence, to fraud or fraudulent misrepresentation, or to any other liability that cannot lawfully be limited.

If a third party brings a claim against us because of what you stored on the platform, what you built on it, or how you used it in breach of these Terms, you will defend and indemnify us against that claim and its reasonable costs. We will tell you promptly, let you control the defence, and cooperate at your expense.

We may change the service and these Terms. Material changes to the Terms are announced by email to account holders and take effect no earlier than 30 days after the notice, except where a change is required by law or is needed to close a security hole.

Continuing to use the service after a change takes effect means you accept it. If you do not, cancel before it does.

These Terms are governed by Greek law. The courts of Athens, Greece have jurisdiction, except that a consumer may also bring proceedings in the courts of their own country of residence and keeps the protection of the mandatory law that applies there.

Talk to us first - most disputes end in an email thread. We do not link to the EU Online Dispute Resolution platform: it ceased operating on 20 July 2025 and pointing consumers at a dead service would be misleading.

• -If a provision is unenforceable, the rest stays in force
• -Failing to enforce a right is not a waiver of it
• -You may not assign this agreement without our consent; we may assign it as part of a merger or sale of the business
• -These Terms, the Data Processing Agreement, and the pricing page are the entire agreement between us on their subject matter
• -Neither party is liable for failure caused by events genuinely outside its control