Prices and billing

The subscription prices, why resource prices are set per region, what is paid ahead and what by the hour, what happens when credit runs out, and how to get an invoice.

Two kinds of price exist on ISOGrid. The subscription has public starting prices, listed below. Resources (an application of a given size, a database, a namespace) are priced per region by the operator of that region, so there is no single national tariff to print here. What this page can do, and does, is tell you exactly how each kind of thing is billed and where to read its price before you commit to anything.

Subscription prices

Commitment	From
1 month	5,000 DZD
3 months	14,000 DZD
6 months	25,000 DZD
12 months	45,000 DZD (3,750 DZD per month)

These are starting prices and they exclude taxes. What your subscription covers is agreed with the team when you subscribe.
Support and maintenance outside the scope of the subscription: 2,800 DZD per hour.
Installing ISOGrid on your own servers (ISOGrid Nomad) is quoted per project.

Why resources have no single price list

A region is a separate set of machines with its own costs, and each region's operator sets what things cost there: every application size, every database arrangement, storage, managed services, Kubernetes capacity, and each kind of machine you can bring through an integration. Two regions can sell the same size at different prices.

Two consequences worth knowing:

Nothing can be created without a price. If a product has not been priced in a region, it is not for sale there: the console says so and the request is refused, rather than letting you start something nobody has put a price on.
Zero is a price. Something shown as free in a region is free there on purpose.

Where to see the exact price

In the console, before you confirm. The creation form shows the sizes on offer in the region you picked and what each costs. Nothing is charged until you confirm.

On the Usage page, afterwards: your balance, every movement on it, and what was spent over a period.

Through the API, if you want the figures in a script:

Call	What it returns
`GET /pricing/applications/{cluster_id}`	The instance types of a region, with their prices.
`GET /pricing/services/{cluster_id}`	The sizes of databases, managed services and the other sized products in a region.
`GET /pricing/availability/{cluster_id}`	Which products the region sells, and which have no price yet.

See REST API for how to call them.

Credit

What the platform charges is taken from your organization's credit: a balance you top up, which consumption draws down.

Topping up goes through the team. There is no card payment in the console today. You pay the team, and the team adds the credit to your organization.
The console warns you when the balance is low, and the owners and administrators of the organization are notified, by email as well, when a renewal could not be paid.
Billing belongs to people. A CLI credential can never touch it.

Currencies

Prices are set in dinars (DZD), euros (EUR) and US dollars (USD), each one by the operator; the console shows them in your currency. When a figure in your currency was converted rather than set, it is marked as approximate.

Your credit is kept as a single balance, in US dollars. A price that exists only in dinars is converted at the moment it is charged, and the amount actually taken is recorded, so a later change of exchange rate cannot make a refund wrong.

What is paid 30 days ahead

Ready-made solutions (a shop, a site, a business application) and the database bought with one, applications deployed from the Store, and each machine added through an integration (or each cluster connected through the Nomad agent) are prepaid by period.

A period is 30 days, not a calendar month, so the same price always buys the same time.
The first period is charged when you create it, before anything is provisioned. Without enough credit, the creation is refused and nothing is left half-made. A machine is charged once it has joined, not before.
Renewal is automatic, at the price in force that day. A size that has since been withdrawn from sale keeps renewing at what you last paid: you are not moved off a plan because it is no longer offered to new customers.
Changing size refunds the unused part of the current period and charges a fresh full period at the new size. You only need credit for the difference.
Deleting refunds the unused part of the period.

If a renewal cannot be paid

The owners and administrators are told, once.
The service keeps running for 3 days. The charge is retried every hour, so topping up within those days is all it takes.
After 3 days it is stopped. It is not deleted: its data, its volumes and its database are untouched.
As soon as the balance covers the renewal, it is started again on its own. Days it spent stopped are not charged. Something you stopped yourself stays stopped.

A machine added through an integration is the exception: it is never switched off automatically, because it may be carrying your whole cluster. The team contacts you instead.

What is paid by the hour

Kubernetes namespaces. You pay for the capacity you reserved (vCPU, memory and storage), at the region's hourly rates, whatever your workloads actually use. Each hour is paid at its start, so you are never more than one hour ahead. Making a namespace bigger charges the difference for the rest of the current hour. If an hour cannot be paid, the namespace keeps running for 24 hours while the charge is retried; after that it is suspended: workloads are scaled to zero, storage is kept, and nothing is charged while it is suspended. It resumes by itself the first time an hour can be paid.

AI Studio sandboxes. A sandbox is billed by the hour, at the start of each hour, only while it is running. A paused sandbox costs nothing, and it pauses by itself after 15 minutes without activity. A sandbox is not stopped for lack of credit: the hour is recorded as an amount you owe (see below). See The AI Studio sandbox.

The assistants

The coding assistant in AI Studio and the DevOps Agent are billed on what they consume, measured in tokens: the text sent to the model and the text it writes back. The Usage page shows it, per member if you want.

Every new account receives 1 million input tokens and 1 million output tokens for the assistants, free, used before anything else. Accounts that already existed when this was introduced, in October 2026, did not receive it. The Usage page shows what is left.

With no credit and no allowance left, the assistant either stops until you top up or, when the platform's limited free mode is switched on, carries on within a daily allowance. Usage in that mode is not free: it is recorded as an amount you owe (see below).

Applications, databases, storage and services ordered on their own

Applications you deploy from your own code or image, database servers, databases on a shared server, object stores and the managed services (identity server, message brokers, cache) each carry a price per size for a 30-day period, shown before you create them, and they cannot be created in a region that has not priced them.

How these are invoiced is part of what you agree with the team when you subscribe. If a figure matters to your decision, ask for it in writing before you build on it.

The free trial

An organization you create yourself by signing up gets a 24-hour trial.

During the trial, with no credit, you can still create what the guided tour builds, and the assistant works on the ordinary models up to a set budget. The price of all of it is recorded as an amount you owe, not charged. Nothing is withheld during the trial.
If you top up, the trial stops mattering: what you built stays, and the amount owed is settled first out of the credit added.
If the 24 hours pass with no top-up, nothing new can be created, and what the trial created (applications, databases, services, Studio projects) is removed. The amount owed stays on the account for the day you do top up.
One trial per person and per device. An organization created by the team for you has no trial and none of this applies to it.

Do not put anything you need to keep into a trial you do not intend to fund.

When credit runs out

What	What happens	What is kept
Solution, its database, Store application	Runs 3 more days, then is stopped; restarts by itself once paid.	Everything. Nothing is deleted.
Machine added through an integration	Keeps running; the team contacts you.	Everything.
Kubernetes namespace	Runs 24 more hours, then is suspended; resumes by itself once paid.	Storage and configuration.
Studio sandbox	Keeps running; the hours are recorded as owed.	Everything.
Creating something that is prepaid	Refused, with the amount that was needed.

Owing money

Outside a trial, an amount you owe holds three things back until it is settled: pushing code from AI Studio to GitHub, making anything publicly reachable, and the file editor in AI Studio. Deploying privately, building, and working with the assistant are not affected, and you can always switch public access off. Credit you add settles what you owe before it becomes spendable.

Refunds

Refunds described on this page go back to your credit balance, not to a bank account: the unused part of a 30-day period when you resize or delete, in proportion to the time left. They are calculated from what you actually paid, never from today's price.

Getting money back out of a credit balance is not something the console does. Ask the team.

If the platform itself was at fault, the remedy is credit, on request: see Availability and support.

Invoices and quotes

An invoice. On the Usage page, choose Request an invoice, say what should be invoiced and leave a phone number. The team calls you back.

A quote, for an installation on your own servers, a longer commitment, or work outside the subscription: write to the team through the contact details on skyvault.pro.