Run your agents and tools on infrastructure we manage. Start with the free Developer Preview.
during Developer Preview
For evaluating Golem, trying integrations, and building prototypes.
Resource limits apply. Contact us to check capacity for your workload.
Start buildingpaid service is not available yet
Planning a production deployment? Talk with us about your workload and requirements.
A dollar estimate needs the rates and terms for paid Cloud.
Discuss your workloadGolem 1.6 measures execution work, active memory, and active filesystem space. These are the resource dimensions planned for paid Cloud; rates are not yet published.
Execution consumes compute. Allocated memory and filesystem space continue to accrue usage while an agent remains active, including during an external wait.
These four resource meters stop accruing. An agent’s age is not its active time. This does not promise unlimited data retention.
An agent run has no fixed resource cost. Measure a representative workload before extrapolating to a month of traffic.
Exercise the code paths and payload sizes you expect to run. Separate active work from time spent suspended.
Record GCU, active memory, and durable and ephemeral filesystem usage. Include expected monthly volume and peak capacity.
Share your measurements, launch timing, retention needs, and support or private-deployment requirements. Rates and paid availability remain unannounced.
Golem Cloud runs your agent code and tools. Budget separately for model APIs and other services billed through your provider accounts.
Operate Golem on your own infrastructure. You supply the compute, storage, and operations. The repository contains the software license and setup instructions.
View on GitHubThe packaged Cloud On-Prem offer is planned. Discuss your cloud, Kubernetes, support, and security requirements with us.
Discuss private deploymentNo. The managed service is free during Developer Preview for evaluation and prototyping. A permanent free production allowance has not been announced. Paid availability, rates, and included quantities will be published when defined.
The consequence depends on the limit. In Golem 1.6, configured monthly compute or call limits can suspend durable agents and fail ephemeral execution. Per-agent memory or managed-filesystem limits can reject allocations or writes. Account limits can reject creation of additional resources. Contact us to confirm the limits that apply to your Cloud workload.
No. Resource limits and application quotas are not a whole-bill spending cap. In the 1.6 metering model, monthly memory and filesystem usage are measured without a corresponding monthly runtime cap. Application quotas govern operations your code explicitly reserves; they do not automatically cap model-provider invoices.
A GiB is 1,073,741,824 bytes. Memory is allocated GiB multiplied by active seconds. Filesystem usage is allocated space multiplied by active time, normalized to a 730-hour month. The 1.6 usage API labels these binary-based quantities GB-seconds and GB-month. Usage is reported by UTC calendar month.
Paid Golem Cloud is not available yet. Discuss your expected volume, measured resource usage, peak capacity, retention, and support requirements with us. A production budget will need published rates and commercial terms. Preview has no SLA or retention guarantee and must not be used for production workloads.
Deploy a prototype, exercise its real workload, and see how it behaves.