Website-Bedingungen

These terms govern your use of capydb.dev and docs.capydb.dev as a visitor. If you have an account, the Terms of Service govern the service itself and take precedence over anything here that conflicts.

Using the site means accepting these terms. If you do not accept them, do not use the site.

Read it, quote it, link to it, and use the code samples in your own projects. Documentation snippets are published so you can copy them, and nothing on the site requires attribution to be reused as a technical example.

Automated access is welcome within reason. We publish machine-readable mirrors precisely so agents and crawlers do not have to scrape the HTML: llms.txt, agents.md, the markdown mirrors of the marketing pages, the full documentation corpus, and an RSS feed for the changelog. Respect robots.txt, identify yourself with a real user agent, and keep request rates reasonable.

• -Interfere with the site's operation, or attempt to gain unauthorized access to any part of it
• -Scrape at a rate that degrades service for anyone else, or evade rate limits
• -Republish the site's content as your own, or present it as if it originated elsewhere
• -Use the CapyDB name, logo, or visual identity in a way that implies endorsement or partnership
• -Use the site to distribute malware, phishing pages, or unlawful material

The text, design, illustrations, and typography of the site are ours or licensed to us. The CapyDB name and logo are ours. Editorial and press use of the marks is covered by the brand assets page, which sets out what you may do without asking.

Open-source projects we publish are governed by the licences in their repositories, not by this page.

The site links out to documentation, registries, package hosts, and platform partners. We do not control those destinations and are not responsible for their content or their privacy practices.

We try to keep the site accurate and current, and the machine-readable mirrors are generated from the same sources the pages render from so the two cannot silently disagree. Even so, the site is provided as-is: benchmark figures, roadmap statements, and documentation describe the platform as we understand it at the time of writing, and are not contractual commitments.

The operative statement of what a plan includes is the pricing page; the operative statement of the agreement is the Terms of Service.

We may update these terms. The revision date at the top of the page is the current version; continuing to use the site after a change means accepting it.

Greek law governs these terms, with the courts of Athens having jurisdiction, without prejudice to the mandatory protections a consumer keeps in their own country of residence.