The terms for using Orkestia.
Version 1.5 · In effect since 26 September 2026Ler em português
What these terms cover
These terms govern your use of orkestia.dev and the Orkestia services made available through its subdomains, including the application, API, and MCP service. By using them, you accept these terms. If you do not, please stop using the services.
An agreement with your organization may add to these terms. Where a signed organization agreement conflicts with these terms, that agreement controls for the organization's use of the platform.
Who you are dealing with
- Publisher: LTINTEG SOFTWARE LTDA - EPP — CNPJ 45.337.609/0001-99
- Contact: hello@orkestia.dev
Using Orkestia
The public site is free to read. You may read it, quote it with attribution, link to it and share it. Platform access requires a valid Orkestia account and the permissions assigned by your organization.
Please do not:
- attempt to gain access to anything the site does not publish, or probe, scan or test the security of the infrastructure behind it without our written permission;
- automate requests at a volume or rate that degrades the service for other people;
- copy the site's look, copy or structure to present it as your own product or to impersonate Orkestia;
- use the site to break a law or someone else's rights.
- use the platform, API, or MCP service to bypass authorization, access another organization's data, or interfere with the service;
Automated reading is welcome within reason. If you build agents or crawlers, /llms.md is published for exactly that purpose and is cheaper for both of us than scraping the rendered pages.
Workflows, integrations, and AI clients
Orkestia executes typed workflows using the integrations your organization has connected and authorized. You are responsible for choosing the workflow, reviewing its inputs and effect, and ensuring you have authority to use the data and third-party account involved. A workflow may read, create, change, delete, publish, or send data in a connected service according to its definition and the permissions granted to it.
The MCP service at https://mcp.orkestia.dev lets a compatible AI client invoke Orkestia tools after authentication. Orkestia does not provide the AI model: you or your organization choose the client and provider. Review that provider's terms, privacy settings, and permissions before sharing conversation context or allowing actions.
Do not provide payment-card numbers or CVV, passwords, private keys, authentication secrets, one-time codes, health information, biometrics, or government identifiers through chat or MCP unless a specific product explicitly requires it and explains the applicable authorization or consent.
Access and actions
Keep your account and connected-provider credentials secure, and revoke access when it is no longer needed. You may disconnect an app or provider connection, and organization administrators may control member access and integration permissions. You remain responsible for actions you authorize through your account, API credentials, or an AI client; use confirmation and approval controls for consequential workflows.
The capability catalog
The catalog lists the capabilities the platform registers. It is published for information, and refreshed each time the site is built, so at any moment it may lag behind what the platform actually offers.
A capability appearing in the catalog is a description, not a promise: it is not an offer, not a service-level commitment, and not a guarantee that it will exist, behave identically, or remain available to a given organization. Entries may be added, changed or removed without notice.
What the pricing page is
The pricing page prints the published plan: one plan for every customer, at the same rates, with no negotiated pricing. Amounts there may change, and the agreement signed with each organization is what binds either side.
Intellectual property
The Orkestia name and logo, the copy, the design and the code of this site belong to us and are protected by Brazilian and international law. These terms grant you no licence to them beyond reading and quoting the site as described above.
Third-party names and marks that appear here — cloud providers, code hosts, AI vendors and other integrations — belong to their respective owners and are used to identify what Orkestia connects to. Their appearance implies no endorsement or partnership beyond what we state explicitly.
Links to other places
The site links to products, documentation and repositories we do not control, including sites run by our customers and partners. We are not responsible for their content, their availability or their privacy practices. Following a link takes you under their terms, not ours.
Availability and accuracy
We write this site carefully and keep it current, but it is provided as it is: we do not warrant that it will be uninterrupted, error-free, or that every statement on it is complete and accurate at the moment you read it. To the extent the law allows, we are not liable for loss arising from your use of, or reliance on, this website. Nothing here limits liability that Brazilian law does not allow us to limit, including under the Consumer Protection Code where it applies.
Privacy
What Orkestia processes about you, why, and how to exercise your rights is set out in the privacy policy and, for LGPD specifically, on the LGPD page. Both are part of these terms.
Changes to these terms
We may update these terms as the site changes. The version and effective date at the top of the page always say which text is current, and continuing to use the site after a change means you accept the new version.
Governing law
These terms are governed by the laws of the Federative Republic of Brazil, including the Marco Civil da Internet (Lei nº 12.965/2014) and the LGPD (Lei nº 13.709/2018). Before anyone goes near a court, write to hello@orkestia.dev — most things are settled in an email.
