Public prices, per minute or per vCPU

The code of both platforms is open source, under the Apache 2.0 license: you can install and use it without us, with no subscription and no royalties. What you pay for is the vendor at your side: SaaS, the pilot, the subscription and graal Services.

Yes. The Data Platform and the Agentic Platform are independent: each one installs, runs and is bought on its own. They complement each other if you take both: the Agentic Platform’s agents operate the Data Platform through its MCP server, under a service account scoped to one project.

Because running a platform in production takes more than code: someone who answers, security fixes, updates the vendor has qualified before offering them to you, signed images whose origin you can verify. You can also do without: no subscription is required to use the software.

Billing runs from the effective start of the workload, meaning its first moment in execution, to its end, per started minute: 61 seconds count as 2 minutes. Time spent in the queue or pulling an image is not billed, and neither is a workload that never started.

Yes, up to the cancellation: the minutes elapsed since the effective start are due, like for a run that completed.

The same as for a job: the reserved instance type multiplied by the minutes it runs. There is one rate, whatever the usage. Workspaces, endpoints, warehouses and managed streams are closed out every month so the invoice follows the period.

Yes. In SaaS, the current month’s costs are visible in the console before the invoice, computed the same way, by project, job, workflow and workspace, with the utilization rate of the reserved resources. On your premises, the platform breaks them down the same way, at your price grid, and exports them for your internal rebilling.

One invoice per month, numbered in a continuous sequence per calendar year (GS-2026-0001, GS-2026-0002…). An issued invoice is never deleted: a mistake is corrected by a credit note, numbered in the same sequence. Payment is manual by default; online payment is an option.

In SaaS, the vendor hosts and operates graal: you pay for usage, by the minute. Self-hosted, graal runs on your infrastructure or at a host of your choice, which you pay directly: you take an annual subscription per vCPU of the execution quota, and no usage invoice is issued in the vendor’s name.

The CPU quota of the execution space, where your workloads run. You set it yourself; a “Subscription” page in the console shows the subscribed vCPU, the quota and the peak actually allocated over the period.

The platform administrator sets their own internal price grid. The platform then computes costs per project, job, workflow and workspace, and exports them. Internal rebilling is included in the subscription.

No. Only reserved compute is billed; storage and outbound traffic are neither measured nor billed.

The prices on this page are those of the public price list. Above 256 vCPU, for an air-gapped deployment or one with source code escrow, or for a tender, we draw up a quote.

Yes, at a fixed price, on one platform or both. It is sized to stay below the procedure exemption threshold for public buyers.

The vendor, GRAAL.SYSTEMS SAS, as part of the subscription. graal Services cover integration, migration, training and operations.

The software is open source: it stays installed on your side and keeps running. Pipeline code is exportable and formats are open: you keep your work and your data.