Terms of Service: Maestro Addendum

MS1. What Maestro Is

Maestro is an AI-powered autonomous development orchestration platform operated by Orchestrel AI SARL ("Maestro" or the "Service"). It enables your team to describe features, plan development tasks, and have AI agents execute, review, test, and integrate code, all running locally on the user's machine.

The Service operates on a dispatch-based billing model: each unit of work (an implementation, a review, or tests written for an implementation) is billed as a "dispatch." Different types of dispatches carry different prices as detailed on our pricing page. Platform access is provided on a monthly subscription basis.

MS2. Accounts, Domains, and API Keys

1. Domain-scoped access. Accounts are scoped to an organizational domain. Up to 25 users on the same domain may access the platform under a single subscription.
2. API keys. Each account receives domain-scoped API keys. You are responsible for maintaining the confidentiality of your keys and for all activity conducted under them.
3. User obligations. Each user must maintain their own machine environment capable of running Maestro's local execution engine.

MS3. Platform Fee and Dispatch Credits

1. Platform fee. A monthly fee of 25 EUR (VAT included) grants access to the platform for up to 25 users, including the dashboard, orchestrator engine, Jira connector, and 25 API keys. Inference (dispatches) is billed separately. All prices are VAT inclusive; where a different tax rate or exemption applies, the final amount is calculated at checkout.
2. Dispatch credits. AI compute is billed on a pre-funded credit basis. You purchase credits in advance and each dispatch deducts from your balance as published on our pricing page.
3. Billing cycle. Platform subscriptions are billed monthly. Credits are charged at the time of purchase.
4. Annual option. Subscribers who commit to a 12-month plan receive 25 EUR in dispatch credits included on top of their subscription.
5. Balance checks. You are responsible for monitoring your credit balance. The Service does not automatically charge more credit. If your balance reaches zero, dispatches will pause until credits are replenished.

MS4. Data Handling

1. Code runs locally. All source code execution, file generation, and code modification occur on your machine. No code is uploaded to or stored on Orchestrel servers.
2. Prompt storage. Orchestrel stores conversation prompts and internal orchestration prompts to ensure session continuity. Prompts are encrypted in transit within the Maestro ecosystem. We do not use your prompts for training or any purpose other than delivering the Service to you.
3. No code storage. Orchestrel servers do not store source code, file contents, or generated artifacts. The orchestration layer operates on metadata (task status, dispatch results) only.
4. Telemetry. We collect usage metrics (dispatch counts, feature completion rates, build duration, and aggregate service usage statistics) for billing and service improvement. No code content is included.

MS5. Cancellation and Credits

1. Cancellation. You may cancel your subscription at any time. Cancellation takes effect at the end of your current billing cycle; you retain access until then.
2. Unused credits. Pre-funded dispatch credits are non-refundable. Upon cancellation, you retain access to your credits until the end of your subscription or until they are exhausted, whichever comes first.

General cancellation and termination rules are in the Terms of Service.