Vinexelcloud documentation
Authenticate with IAM Central, then use your project-owned cloud workspace. Owners grant only the permissions needed for each registered identity.
Workspace and identity
Verify the account
Connect your Git repositorySave the Leaseweb credential in Integrations. Verify the account contract, regions, Linux images and instance types before publishing an orderable product.frontendbackendDocker container
Choose a published plan, a server name and a public SSH key. A funded USD balance, explicit spending admission and resource quota are required.AI-generated projects →
Deploy compute
Create agentsKeep the request key when retrying. Confirmed means the provider accepted a mutation or answered a read. Start and stop require their desired observed state; termination requires a verified final contract. A successful refresh does not prove an uncertain reboot occurred.popular LLMsknowledge baseMCP servers
Stopping an instance does not end its contract. Termination is irreversible. Final retail usage requires a verified contract end; provider expense evidence is a separate financial record.Get started with AI Agents →
Asynchronous operations
Tariffs use USD. Flymebase issues a saved IDR settlement quote. Only a matching verified paid Qrisbill transaction grants credit. Credit activity shows posted payments, deployment reserves, additional usage, reserve refunds and payment reversals, with UTC date and category filters.
Issue infrastructure read or operation access separately from cloud:billing:read. Keys expire after 90 days; their digest is stored instead of the secret. Infrastructure reads, queue admission and final worker dispatch recheck current membership, expiry, scope and revocation under the workspace lock. Revocation before dispatch admission rejects queued work; requests admitted for dispatch may already be in flight and cannot be recalled. Resource responses expose observation.verified_at and refresh_required so retained state is not mistaken for a new observation.Browse Marketplace →
Stop and terminate
Compute is the first lifecycle adapter. Managed databases, app hosting, Kubernetes, networking, object storage and marketplace automation are planned and cannot currently be ordered.
Unknown mutations are never automatically repeated. Owners and administrators can review uncertain start, stop and reboot outcomes using a fresh stable observation, a provider evidence reference and recorded findings. This attestation changes neither infrastructure nor charges; create and terminate require verified provider reconciliation.Go to Managed Databases →
Payment and exchange rates
Authenticate with IAM Central, then use your project-owned cloud workspace. Owners grant only the permissions needed for each registered identity.
Save the Leaseweb credential in Integrations. Verify the account contract, regions, Linux images and instance types before publishing an orderable product.Check our Managed Kubernetes guides →
Scoped API credentials
Choose a published plan, a server name and a public SSH key. A funded USD balance, explicit spending admission and resource quota are required.
Keep the request key when retrying. Confirmed means the provider accepted a mutation or answered a read. Start and stop require their desired observed state; termination requires a verified final contract. A successful refresh does not prove an uncertain reboot occurred.Cloud ServersManaged DatabasesObject StorageLoad Balancers
Service boundary
Stopping an instance does not end its contract. Termination is irreversible. Final retail usage requires a verified contract end; provider expense evidence is a separate financial record.
ProjectsTariffs use USD. Flymebase issues a saved IDR settlement quote. Only a matching verified paid Qrisbill transaction grants credit. Credit activity shows posted payments, deployment reserves, additional usage, reserve refunds and payment reversals, with UTC date and category filters.
Users and Permissions →