| 1 | --- |
| 2 | title: Usage and billing |
| 3 | description: What is free on g1t, what the g1t plan costs and includes, how compute is paid for, the limits that keep spend in check, and enterprise billing. |
| 4 | --- |
| 5 | |
| 6 | The forge is free: repositories, git, work items, pull requests and review cost |
| 7 | nothing, for public and private work. What costs money is compute, the |
| 8 | things g1t runs for you: the sandboxes your workflows and checks run in, |
| 9 | deployed apps, and, on the plan, storage and git traffic past the free |
| 10 | amounts. Each is priced from what it costs g1t, plus 20%: runner minutes |
| 11 | at a fixed rate for each machine, everything else at its cost plus 20%. |
| 12 | It is charged to the workspace that owns the repository. There is no seat price. |
| 13 | Your spend limit bounds paid usage; public storage and service size limits still apply. |
| 14 | |
| 15 | Wherever this page says an owner can do something to a workspace's |
| 16 | billing, so can its [billing managers](/guides/workspaces/#roles-that-add-to-a-member): |
| 17 | starting or ending the plan, the spend limit and budget alerts, |
| 18 | prepaying, the card and billing details. Deleting the |
| 19 | workspace stays with owners. |
| 20 | |
| 21 | ## What is free |
| 22 | |
| 23 | Every workspace, with or without the plan, has [Chat](/guides/chat/) and |
| 24 | the whole forge: |
| 25 | |
| 26 | - Channels, direct messages, threads, mentions and live delivery, with no |
| 27 | limit on history. People chatting is never charged. |
| 28 | - Public and private repositories, git, work items, pull requests and reviews. |
| 29 | - Protected branches, code owners and secret push protection. |
| 30 | - [Security scans](#storage-search-embeddings-and-scans) of history and |
| 31 | dependencies, which g1t pays for on a free workspace. |
| 32 | - Search and Explore. |
| 33 | - The [audit log](/guides/audit-log/), with export: kept 7 days, or 90 on |
| 34 | the plan. |
| 35 | - Your own coding agent through [MCP](/reference/mcp/). |
| 36 | - 1 GB of private repository storage, 5 GB of public repository storage, |
| 37 | and 50,000 [git operations](#git-operations) a month. |
| 38 | |
| 39 | None of this is charged, on the plan or not. A free workspace is never |
| 40 | charged for storage: once its private repositories hold 1 GB, pushes to |
| 41 | them are refused at the start of the push, with what to do: make the |
| 42 | repository public, delete what you do not need, or start the plan, where |
| 43 | storage past 1 GB is usage and pushes never stop. Public repositories are |
| 44 | never charged for storage. Every workspace, including paid workspaces, |
| 45 | has a **5 GB public repository storage cap**. Pushes, imports, forks and |
| 46 | changes that would add public storage need room within that cap. |
| 47 | Recently deleted repositories still count until permanently deleted. |
| 48 | In-flight writes reserve capacity; an interrupted write may retain its |
| 49 | reservation until it is reconciled. |
| 50 | |
| 51 | Compute is not free. Workflows, the merge queue, |
| 52 | deployments and semantic search need [the g1t plan](#the-g1t-plan), or a |
| 53 | [card check](#no-card-no-compute) for the trial and the open-source pool. |
| 54 | |
| 55 | ### One free workspace per person |
| 56 | |
| 57 | Each person can own **one free workspace**: a workspace that is not on the |
| 58 | g1t plan, an enterprise's terms or a full discount. A new workspace starts |
| 59 | free, so while you own a free workspace, creating another is refused with |
| 60 | the way forward: |
| 61 | |
| 62 | 1. Start the plan on the free workspace you have |
| 63 | ([Start or end the plan](#start-or-end-the-plan)), or |
| 64 | 2. delete it, if you no longer use it |
| 65 | ([Delete a workspace](/guides/workspaces/)). |
| 66 | |
| 67 | Then create the new one. If you owned several free workspaces before this |
| 68 | rule, you keep them all, but you cannot create another until each of them |
| 69 | is on the plan or deleted. Workspaces you belong to without owning them do |
| 70 | not count. The site's **New workspace** page says so before you start; |
| 71 | `POST /workspaces` and the MCP `workspace` tool's `create` action answer |
| 72 | `402` (`payment_required`) with the same message. |
| 73 | |
| 74 | ### Who a free workspace can add |
| 75 | |
| 76 | A free workspace keeps the people already in it, but **cannot add anyone** |
| 77 | until it starts the plan: |
| 78 | |
| 79 | - no new members, by username or by email invite; |
| 80 | - no outside collaborators on its repositories, and no invitations to them; |
| 81 | - an invite or invitation sent before cannot be accepted until then (it |
| 82 | waits, and works once the plan is on). |
| 83 | |
| 84 | Its members can still be given a role on its repositories, and put on its |
| 85 | [teams](/guides/teams/). On the **Members** and **Invitations** pages and a repository's |
| 86 | **Settings → Access**, an owner sees **Start the plan to invite people** |
| 87 | with a button to the plan. Through the API and MCP, adding a member, |
| 88 | inviting, adding an outside collaborator and accepting are refused with |
| 89 | `402` (`payment_required`). |
| 90 | |
| 91 | Your own machines are. Workflow jobs on |
| 92 | [self-hosted runners](/guides/self-hosted-runners/) cost nothing, on every |
| 93 | plan, the free one included, and need no card; their minutes show on usage |
| 94 | as **Self-hosted runner time** at $0. |
| 95 | |
| 96 | ## The g1t plan |
| 97 | |
| 98 | One plan, **$21 a month per workspace**, however many people are in it. It is never priced per person. Like every price on g1t, it |
| 99 | excludes tax ([Tax](#tax)). There is no card processing fee on top: it is |
| 100 | part of the price. |
| 101 | |
| 102 | - **$10 of usage each month**, used first: everything g1t runs, at the |
| 103 | [prices below](#what-it-costs) (runner minutes at their flat rate per |
| 104 | machine, everything else at cost plus 20%). That is 2,500 runner minutes on the standard machine, or |
| 105 | about 1,428 on `g1t-4core` (which `ubuntu-latest` gets in a public |
| 106 | repository). |
| 107 | - **Everyone in the workspace** at one price, never per person. |
| 108 | - **Unlimited** projects, previews and repositories. |
| 109 | - Workflows, the merge queue, |
| 110 | [deployments](/guides/deployments/), semantic search, and |
| 111 | [Security and quality](/guides/security/pricing/) on private |
| 112 | repositories. |
| 113 | - **90 days** of [audit log](/guides/audit-log/#how-long-it-is-kept), in |
| 114 | place of a free workspace's 7. |
| 115 | - Usage past $10 is charged the same way, **up to your |
| 116 | [spend limit](#limits)**. |
| 117 | |
| 118 | The plan has no count limit on projects or previews. Public repository |
| 119 | storage has the 5 GB cap above, and repository and request size limits |
| 120 | still apply. Paid usage is metered from the |
| 121 | first unit (past the free 1 GB of private storage and 50,000 git |
| 122 | operations that every workspace has). Your spend limit also stops new |
| 123 | paid work. |
| 124 | |
| 125 | **Included usage** pays for the month's usage first, at the same prices as |
| 126 | everything else: runner minutes, builds, app traffic, custom domains, |
| 127 | storage, git operations, search embeddings and security scans. Past it, |
| 128 | usage is charged at the same prices. It starts again on the 1st of each |
| 129 | month (UTC). **Unused included usage does not roll over.** Billing shows |
| 130 | how much of it this month's usage has drawn. |
| 131 | |
| 132 | ### What it costs |
| 133 | |
| 134 | Pricing has two rules: |
| 135 | |
| 136 | 1. **Everything g1t runs at cost plus 20%.** Builds, hosting, storage, |
| 137 | git operations, search and security scans: what g1t pays for them, |
| 138 | plus 20%. [Runner minutes](#runner-minutes) are a fixed rate for each |
| 139 | machine, set the same way: what a minute of it costs g1t with half its |
| 140 | vCPUs busy, plus 20%, rounded up to a tenth of a cent, and never under |
| 141 | its cost with every vCPU busy. |
| 142 | 2. **Your own runners are free.** Jobs on your |
| 143 | [own runners](/guides/self-hosted-runners/) cost nothing here. |
| 144 | |
| 145 | There are no seats. The live figures are on |
| 146 | [g1t.sh/pricing](https://g1t.sh/pricing). |
| 147 | |
| 148 | | What | Unit | Costs g1t | You pay | |
| 149 | | ------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------- | -------------------------------------------------------------- | -------------------------------- | |
| 150 | | [Runner minutes](#runner-minutes) on the standard machine (2 vCPU, 8 GiB, 16 GB): workflow jobs, checks, the merge queue | Minute, each job rounded up | From $0.0014 a minute idle to $0.0038 with both vCPUs busy | $0.004 a minute | |
| 151 | | [Runner minutes](#runner-minutes) on `g1t-4core` (4 vCPU, 12 GiB, 20 GB) | Minute, each job rounded up | From $0.0020 a minute idle to $0.0068 with all four vCPUs busy | $0.007 a minute | |
| 152 | | Deploy builds | Second | About $0.0017 a minute | About $0.002 a minute | |
| 153 | | App requests | Million | $0.30 | $0.36 | |
| 154 | | App CPU time | Million CPU milliseconds | $0.02 | $0.024 | |
| 155 | | Custom domains | Domain-month | $0.10 | $0.12 | |
| 156 | | [Container apps](/guides/deployments/#docker-deployments), while awake | Second, by the minute: vCPU, memory, disk and the Durable Object, by the size | From $0.0129 an hour (`lite`) | Cost + 20%: from $0.0155 an hour | |
| 157 | | Data container apps send | GB | $0.05 | $0.06 | |
| 158 | | Private storage, past the free 1 GB | GB-month | $0.50 | $0.60 | |
| 159 | | [Actions cache](#actions-cache) storage | GB-month | $0.015 | $0.018 | |
| 160 | | Git operations, past the free 50,000 a month | 1,000 | $0.15 | $0.18 | |
| 161 | | Search embeddings | Million tokens | $0.067 | $0.0804 | |
| 162 | | Security scans | Million CPU ms / million rows | $0.02 / $1.00 | $0.024 / $1.20 | |
| 163 | | Projects, previews, apps and repositories | | Next to nothing | Not charged | |
| 164 | |
| 165 | Build seconds follow what Cloudflare bills g1t, so that figure moves a |
| 166 | little; the pricing page always has today's. Runner minutes are fixed |
| 167 | rates. |
| 168 | Actions cache storage is charged at R2's published price, and is not on |
| 169 | the pricing page yet. |
| 170 | |
| 171 | **The other $10** pays for running g1t, the free forge everyone uses, and |
| 172 | the people building it. |
| 173 | |
| 174 | Deployments are part of the plan. There is no separate Deployments |
| 175 | purchase. |
| 176 | |
| 177 | ### Start or end the plan |
| 178 | |
| 179 | Only an owner or a billing manager can start or end the plan. |
| 180 | |
| 181 | 1. Open **Settings → Billing and plans**, `g1t.sh/<workspace>/-/billing`. |
| 182 | 2. On the **g1t** card, choose **Start the g1t plan**. |
| 183 | 3. If the workspace already has a checked card, the plan starts on it at |
| 184 | once. Otherwise, pay on the card page you are sent to. |
| 185 | |
| 186 | Back on Billing, the plan's card says **On the g1t plan** (**first month** |
| 187 | in the first billing cycle), with the usage month and the day the plan |
| 188 | renews: **Usage month Oct 1 – Oct 31, 2026; the plan renews Nov 15, 2026**. |
| 189 | Usage is counted by calendar month (UTC), but the plan renews on the day |
| 190 | of the month it started, so a plan started mid-month renews mid-month. |
| 191 | Then come a meter for the month's included usage, and the **Upcoming invoice**: the plan and add-ons |
| 192 | at their monthly price plus usage still owed after included usage, credit |
| 193 | and any discount, from g1t's own ledger (**View upcoming invoice** splits |
| 194 | it). **Usage** goes to usage by product and project. App traffic, custom |
| 195 | domains, storage and git operations are counted through the month and |
| 196 | charged when it closes. |
| 197 | |
| 198 | To end the plan, choose **Manage billing** and cancel it on Stripe's |
| 199 | billing page: it ends at the end of the period, with nothing more charged |
| 200 | after, and the plan's card says **Ends on** and the date. Until then, |
| 201 | **Manage billing** lets you keep it after all. If a renewal payment fails, |
| 202 | the card says **Payment failed**, and the plan's features stop until it is |
| 203 | paid: choose **Update payment method** and change the card on Stripe's |
| 204 | page. |
| 205 | |
| 206 | Starting the plan uses the card from the card check, or else the default |
| 207 | card on Stripe's billing page, without a second page; with neither, Stripe's |
| 208 | page asks for one. If Stripe refuses, the page says why in a sentence. |
| 209 | |
| 210 | A card that says **100% discount from g1t** or **Included by g1t** is on |
| 211 | under terms g1t set with the workspace, such as a |
| 212 | [100% discount](#enterprises-and-custom-terms), with nothing to pay or end. |
| 213 | |
| 214 | ## No card, no compute |
| 215 | |
| 216 | Compute costs g1t real money from the first second, and free compute |
| 217 | attracts people who use it to mine cryptocurrency. A card check is the |
| 218 | smallest gate that stops that: it puts a real card behind each workspace, |
| 219 | and each card gets one trial. |
| 220 | |
| 221 | A free workspace needs a card check before its trial or g1t's open-source |
| 222 | pool pays for anything. Only an owner can do it. |
| 223 | |
| 224 | 1. Open **Settings → Billing and plans**. |
| 225 | 2. Under **Try it with $5 of usage**, choose **Check a card**. You are sent |
| 226 | to Stripe's card page. |
| 227 | 3. Enter the card. If your bank asks for 3-D Secure, confirm it there. |
| 228 | |
| 229 | The card check is **never charged**: Stripe saves and verifies the card, |
| 230 | and nothing is taken. Back on Billing, a line says whether the trial |
| 231 | started. The card is saved as the workspace's card, so starting the plan |
| 232 | later needs no second card page. |
| 233 | |
| 234 | The trial needs a credit or debit card; prepaid cards can still pay for the |
| 235 | plan. A prepaid card passes the check, and unlocks the open-source pool, |
| 236 | but starts no trial. |
| 237 | |
| 238 | The card check unlocks: |
| 239 | |
| 240 | - [The trial](#the-trial): $5 of usage, once. |
| 241 | - [The open-source pool](#the-open-source-pool): checks, workflows and |
| 242 | the merge queue on public repositories. |
| 243 | |
| 244 | ## The trial |
| 245 | |
| 246 | Once its card is checked, a workspace gets **$5 of trial credit**, once. It |
| 247 | pays for usage at the plan's prices: runner minutes for checks, workflows |
| 248 | and the merge queue (1,250 on the standard machine, about 714 on the |
| 249 | 4-core one), and semantic search. It never pays for deployments. |
| 250 | |
| 251 | - Each card gets one trial, whichever workspace it is checked in. Prepaid |
| 252 | cards start none. |
| 253 | - Trials come from a pool of **$100 a month** for everyone together. It |
| 254 | renews on the 1st of each month (UTC). When a month's pool is given out, |
| 255 | new trials wait until the 1st, and **Settings → Billing** says so. |
| 256 | - Billing shows what is left. |
| 257 | |
| 258 | The trial does not turn into a charge. Nothing is charged until an owner |
| 259 | starts the plan. If a free workspace's last trial run goes past what was |
| 260 | left, g1t covers the difference, and the statement shows it as **Covered |
| 261 | by g1t**. When the trial is used up, new compute waits for the plan. |
| 262 | |
| 263 | ## The open-source pool |
| 264 | |
| 265 | g1t sets aside **$25 a month** for public repositories, at most **$2 a |
| 266 | month** for any one repository: about 3,571 and 285 minutes of |
| 267 | workflow jobs, which run on the 4-core machine in a public repository, |
| 268 | or 6,250 and 500 minutes of checks and merge queue runs on the standard |
| 269 | machine. It pays for **checks, workflows and the merge queue on |
| 270 | public repositories**, after a card check. It does not pay |
| 271 | for deployments, storage or embeddings. |
| 272 | |
| 273 | When the pool or the repository's share is spent, those runs wait for the |
| 274 | next month, or for the plan. Each statement line the pool paid says so, |
| 275 | and the month's statement totals it under **Paid by g1t's open-source |
| 276 | pool**. |
| 277 | |
| 278 | ## What is charged |
| 279 | |
| 280 | | | Charged | |
| 281 | | ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | |
| 282 | | Checks and the [merge queue](/guides/merge-queue/) | [Runner minutes](#runner-minutes) | |
| 283 | | [Workflow](/guides/actions/) jobs | [Runner minutes](#runner-minutes), at the rate of the machine each ran on | |
| 284 | | [Actions cache](#actions-cache) | What it holds, on the plan only | |
| 285 | | [Deployments](/guides/deployments/) | Builds, requests, CPU time, custom domains and container time, from the first. Projects and previews are not charged. | |
| 286 | | [Private repository storage](#storage-search-embeddings-and-scans) | Past the free 1 GB, on the plan only | |
| 287 | | [Git operations](#git-operations) | Past the free 50,000 a month, on the plan only | |
| 288 | | [Search embeddings](#storage-search-embeddings-and-scans) | For private text, on the plan only | |
| 289 | | [Security scans](#storage-search-embeddings-and-scans) | On the plan only | |
| 290 | | Repositories, work items, pull requests, review, search, the API and MCP | No | |
| 291 | |
| 292 | The charge goes to the workspace that owns the repository, whoever |
| 293 | started the work. |
| 294 | |
| 295 | ## Add-ons |
| 296 | |
| 297 | **Billing → Add-ons** lists what comes with the plan beside its usage, and |
| 298 | whether it is on: |
| 299 | |
| 300 | | Add-on | Price | What it adds | |
| 301 | | ---------------------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
| 302 | | Security and quality | With the plan, no price of its own | Custom secret patterns, validity checks, delegated bypass, code scanning, dependency review and the security overview on **private** repositories. Its scans are charged at cost plus 20%. Public repositories get all of it free. | |
| 303 | | Production deployments | With the plan | Previews per pull request and production on g1t.page, metered at cost plus 20%. | |
| 304 | |
| 305 | Secret scanning, push protection, vulnerability alerts, security updates, |
| 306 | the dependency graph and SBOMs are free everywhere, on every plan. See [What's free and what's paid](/guides/security/pricing/). |
| 307 | |
| 308 | ## How prices are set |
| 309 | |
| 310 | Every price is what g1t pays for the thing, at Cloudflare, plus 20%; |
| 311 | [runner minutes](#runner-minutes) are a fixed rate for each machine, set |
| 312 | the same way from what a minute of it costs. The live prices are on |
| 313 | [g1t.sh/pricing](https://g1t.sh/pricing), straight from the price book |
| 314 | billing charges from. |
| 315 | |
| 316 | | Meter | Unit | |
| 317 | | ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | |
| 318 | | Runner minutes | Per minute, each job rounded up, at a fixed rate for each machine | |
| 319 | | Deploy builds | Per second | |
| 320 | | App requests and CPU | Per million requests, per million CPU milliseconds | |
| 321 | | Custom domains | Per domain-month | |
| 322 | | Container apps | Per vCPU-second, GiB-second of memory and GB-second of disk while awake, a second of the Durable Object in front of each, and per GB sent | |
| 323 | | Private storage past the free 1 GB | Per GB-month | |
| 324 | | Actions cache storage | Per GB-month | |
| 325 | | Git operations past the free 50,000 a month | Per 1,000 | |
| 326 | | Search embeddings | Per million tokens | |
| 327 | | Security scans | Per million CPU milliseconds and per million rows written | |
| 328 | |
| 329 | Prices keep themselves current as those costs move. Every day, g1t |
| 330 | checks what Cloudflare billed its account against what was used: |
| 331 | Containers and the Durable Objects behind them against the seconds |
| 332 | containers ran, Workers for Platforms per request and per CPU millisecond. |
| 333 | When a cost moves, the price book moves with it, and the change is listed |
| 334 | on the pricing page with the reason. A large move, or a measurement far |
| 335 | from the current cost, waits for a person at g1t to check it, so one odd |
| 336 | day cannot reprice anything. |
| 337 | |
| 338 | ### How we keep prices at cost |
| 339 | |
| 340 | Prices follow what Cloudflare charges g1t. Every day g1t reads its own |
| 341 | Cloudflare bill and sets it beside what it counted and what it charged |
| 342 | for the same things, product by product, so a price that no longer |
| 343 | matches its cost is found and corrected. |
| 344 | |
| 345 | - **A price that goes down** changes at once. |
| 346 | - **A price that goes up** is announced first: it is listed on |
| 347 | [g1t.sh/pricing](https://g1t.sh/pricing) with the day it takes effect, |
| 348 | and owners of workspaces on the plan are emailed. It takes effect 14 |
| 349 | days later, and for something charged once a month (git operations, |
| 350 | storage, the actions cache, custom domains, embeddings, scans) at the |
| 351 | start of the month after that, so no month is charged at two prices. |
| 352 | - **A new machine** is priced at what it costs from its first minute, so |
| 353 | g1t never charges less than it pays. When the standard machine became |
| 354 | [2 vCPU, 8 GiB and 16 GB](#runner-minutes), its runner minutes and |
| 355 | deploy builds were priced for it at once. |
| 356 | - **Nothing already charged changes.** Each charge records the price it |
| 357 | was made at. |
| 358 | |
| 359 | Some of the Cloudflare products g1t pays for are in beta and do not yet |
| 360 | define exactly what they bill; see |
| 361 | [What g1t can't do yet](/about/limitations/#billing). |
| 362 | |
| 363 | ### Runner minutes |
| 364 | |
| 365 | Every job g1t runs on its own machines (a workflow job, a check, a merge |
| 366 | queue run) is charged by the minute, at a fixed rate for the machine it |
| 367 | ran on: |
| 368 | |
| 369 | | `runs-on` | Machine | vCPUs | Memory | Disk | A minute | |
| 370 | | -------------------------------------------------------------------------------- | ------------------- | ----- | ------ | ----- | -------- | |
| 371 | | `ubuntu-latest` or any other Linux label in a private repository, or `g1t-2core` | Standard (`2-core`) | 2 | 8 GiB | 16 GB | $0.004 | |
| 372 | | `ubuntu-latest` or any other Linux label in a public repository, or `g1t-4core` | `4-core` | 4 | 12 GiB | 20 GB | $0.007 | |
| 373 | |
| 374 | `ubuntu-latest` gets what it gets on GitHub: 4 vCPUs in a public |
| 375 | repository, 2 in a private one. A job is charged as the machine it ran |
| 376 | on. Checks and the merge queue run on the standard machine. `g1t-2core` is |
| 377 | kept as a name of the standard machine, so workflows that ask for it keep |
| 378 | working, at its rate. |
| 379 | |
| 380 | **How a job's minutes are counted.** Each job's time, from when its |
| 381 | machine starts to when it stops, is rounded up to the whole minute: a |
| 382 | job of 61 seconds is 2 minutes, and any job that ran is at least 1. Each |
| 383 | job is rounded on its own, so a run of three 20-second jobs is 3 |
| 384 | minutes. There are no free minutes outside the plan's |
| 385 | [included usage](#the-g1t-plan), the [trial](#the-trial) and the |
| 386 | [open-source pool](#the-open-source-pool), which pay for minutes at these |
| 387 | rates. |
| 388 | |
| 389 | **Why these rates.** Cloudflare bills g1t for a machine's memory and disk, |
| 390 | and the Durable Object behind it, for every second it runs, busy or idle, |
| 391 | and for its CPU as it is used. Each rate is what a minute of the machine |
| 392 | costs g1t with half its vCPUs busy, plus 20%, rounded up to a tenth of a |
| 393 | cent, and never under what it costs with every vCPU busy: |
| 394 | |
| 395 | | Machine | Costs g1t a minute, idle | With half its vCPUs busy | With every vCPU busy | A minute | |
| 396 | | ------------------- | ------------------------ | ------------------------ | -------------------- | -------- | |
| 397 | | Standard (`2-core`) | $0.0014 | $0.0026 | $0.0038 | $0.004 | |
| 398 | | `4-core` | $0.0020 | $0.0044 | $0.0068 | $0.007 | |
| 399 | |
| 400 | Should a job ever cost g1t more than its minutes at the rate, it is |
| 401 | charged that cost instead. A build that compiles often finishes several |
| 402 | times sooner on `g1t-4core`, so it can cost about the same. |
| 403 | |
| 404 | Each job is one line on the [statement](#the-statement), naming its |
| 405 | machine and minutes, such as _A workflow job in acme/api on g1t-4core: |
| 406 | 6m 40s, 7 minutes on the 4-core machine_. Usage, the statement and the API |
| 407 | total them as **Runner minutes, 2-core** and **Runner minutes, 4-core**; |
| 408 | months before runner minutes show **Sandbox time**, by the second. |
| 409 | Deploy builds are not counted here: [Deployments](/guides/deployments/) |
| 410 | charges them by the second, from the first, under **Builds**. Jobs on |
| 411 | [your own runners](/guides/self-hosted-runners/) are free: they show as |
| 412 | **Self-hosted runner time** at $0. |
| 413 | |
| 414 | ## Git operations |
| 415 | |
| 416 | Cloudflare charges g1t **$0.15 per 1,000 git operations** from 2026-10-14. |
| 417 | An operation is one clone or fetch (a request that fetches objects) or one |
| 418 | push, and making, forking or deleting a repository: what Cloudflare bills |
| 419 | g1t for. Listing refs, and anything g1t answers from its own cache, is |
| 420 | never an operation: a repeat clone of the same commit is served from |
| 421 | g1t's [pack cache](/guides/git/#where-a-slow-requests-time-went) and is not |
| 422 | counted. g1t meters every request it makes to the store, and |
| 423 | what counts follows what Cloudflare confirms it bills; this page changes |
| 424 | with it. |
| 425 | |
| 426 | Checks, builds and workflow jobs clone, fetch and push through the same |
| 427 | git endpoints you use, and count the same as yours, as does any coding |
| 428 | agent you connect. Each counts for the workspace whose repository it is. |
| 429 | A pull request's working copy counts for the workspace of the repository |
| 430 | the pull request is in. g1t's own nightly |
| 431 | backups are never counted for your workspace. |
| 432 | |
| 433 | | | Each month (UTC) | |
| 434 | | --------------------------- | --------------------------------------------------------- | |
| 435 | | Free, on every workspace | 50,000 | |
| 436 | | On the plan, past 50,000 | $0.18 per 1,000 (cost plus 20%). Never slowed or refused. | |
| 437 | | Free workspace, past 50,000 | Not charged. Slowed to 60 an hour until the month turns. | |
| 438 | |
| 439 | 50,000 is far more than an active workspace uses. A workspace on the plan pushes and clones on past it and pays for |
| 440 | what it uses, up to its spend limit. A free workspace is never charged for |
| 441 | git operations: past 50,000 in a month, its git requests past 60 in an |
| 442 | hour are answered `429` with when to try again. |
| 443 | |
| 444 | Charging starts on 2026-10-14: operations before then are never charged. |
| 445 | **Billing** shows this month's count under **Git operations & storage**. |
| 446 | |
| 447 | A month's operations are charged in full, up to its last minute: its |
| 448 | final count is taken once the month has ended (from an hour after |
| 449 | midnight UTC on the 1st), and the month is charged and closed only after |
| 450 | that, at the plan the workspace had that month. |
| 451 | |
| 452 | ## Storage, search embeddings and scans |
| 453 | |
| 454 | These are counted through the month and charged once it is over, as one |
| 455 | line dated the month's last day, so the limit counts them as they happen. |
| 456 | The plan's included usage and the trial pay for them first. |
| 457 | |
| 458 | Security scans and search embeddings run on every workspace, with or |
| 459 | without the plan. On a free workspace g1t pays for them itself. They appear on the statement at $0, _covered by g1t_, never count |
| 460 | toward the limit and never use the trial. |
| 461 | |
| 462 | | | What it costs g1t | What is counted | |
| 463 | | -------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | |
| 464 | | Private repository storage | $0.50 a GB-month (Cloudflare Artifacts) | On the plan, each day, what the workspace's private repositories hold past the free 1 GB. A month's GB-months are those days added up, divided by the days in the month. | |
| 465 | | Search embeddings | $0.067 per million tokens (Workers AI) | The text of private repositories, work items and pull requests put in the search index. Public text and searches are not charged. | |
| 466 | | Security scans | $0.02 per million CPU milliseconds and $1.00 per million rows written (Workers and D1) | The CPU each history scan and dependency check takes and the rows it writes. | |
| 467 | |
| 468 | ### Actions cache |
| 469 | |
| 470 | What a workspace's [`actions/cache`](/guides/actions/#the-cache) entries and its runs' |
| 471 | [artifacts](/guides/actions/#artifacts) hold is measured every hour, and each day's largest figure counts. A |
| 472 | month's GB-months are those days added up, divided by the days in the month, charged at |
| 473 | $0.018 a GB-month: R2's $0.015, plus 20%. It is charged from the first |
| 474 | byte, to workspaces on the plan only, as **Actions cache storage** under |
| 475 | **Git operations & storage**. A free workspace's caches are never charged; |
| 476 | they are held to the same 10 GiB a repository, and 10 GiB of artifacts a run, as everyone's. |
| 477 | |
| 478 | ### Private repository storage |
| 479 | |
| 480 | Storage is charged at $0.60 a GB-month (cost plus 20%). It is measured from |
| 481 | the packs pushed through g1t's git endpoints to each repository and its |
| 482 | pull requests' working copies, so what is charged is never more than what |
| 483 | is stored. Public repositories are never charged, and neither is a free |
| 484 | workspace: its pushes to private repositories stop at 1 GB instead. On the |
| 485 | plan they never stop. |
| 486 | |
| 487 | A [fork](/concepts/forks/) counts toward the workspace it was forked into |
| 488 | in full, from the moment it is made: its size is what was copied into it, |
| 489 | however much it shares with the repository it came from. A free workspace |
| 490 | cannot take a private fork that would carry its private repositories past |
| 491 | 1 GB. Pull requests' working copies are counted with the repository they |
| 492 | belong to. |
| 493 | |
| 494 | ## How spend is counted |
| 495 | |
| 496 | Everything a workspace uses is entered on one ledger, as it happens, and |
| 497 | every figure on every page is read back from it. There is no second count |
| 498 | to disagree with it. |
| 499 | |
| 500 | | Figure | What it is | Where it shows | |
| 501 | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | |
| 502 | | **Spent**, or usage **at price** | Every entry at its price: what was charged, plus what the plan's included usage, the trial, a pool or g1t paid of it, plus what a discount took off. The one measure of usage. | The [Usage page](#the-usage-page), the [statement](#the-statement) | |
| 503 | | **Charged** | What is left for the workspace to pay this month: usage at price, less your discount, less what included usage, the trial, a pool or g1t paid, less what [credit](#credits-from-g1t) paid. Never below zero: a workspace with a 100% discount is charged exactly nothing. Usage metered through the month and charged when it closes (storage, git operations, scans, embeddings, domains, app traffic) counts now on the same terms. | Billing's plan card, and the figure your [spend limit](#your-spend-limit) is measured against | |
| 504 | |
| 505 | **This month** is the calendar month in UTC, from its first day to today, |
| 506 | on every page: Billing's plan card and Usage's current billing cycle ask |
| 507 | billing for the same days and show the same figure. Usage metered through the month and |
| 508 | charged when it closes (storage, git operations, scans, embeddings, |
| 509 | domains, app traffic) has no day of its own, so it counts in any range |
| 510 | that reaches into the current month, and Usage's receipt says what of it |
| 511 | will be charged at the close on your terms: your discount and included |
| 512 | usage come off it then, the same as the rest. |
| 513 | |
| 514 | Every amount is written the same way: to the cent, rounded half up on |
| 515 | whole millionths of a dollar, so the same sum never reads differently on |
| 516 | two pages. Under a cent reads **<$0.01** rather than $0.00 on a total, |
| 517 | and exactly nothing is $0.00. Where the fraction of a cent is the point, |
| 518 | the [statement](#the-statement) and the |
| 519 | [price book](https://g1t.sh/pricing), amounts carry up to four places |
| 520 | (`$0.0063`). |
| 521 | |
| 522 | Through the API, `GET /workspaces/:workspace/usage` answers with the |
| 523 | products and `totals.charged_micros`, with `totals.pending_charged_micros` for what of the pending usage the close will charge; |
| 524 | `GET /workspaces/:workspace/budget` answers with the spend limit and |
| 525 | `spent_micros`, the same charged figure. |
| 526 | |
| 527 | ## Limits |
| 528 | |
| 529 | Every workspace has two limits: **g1t's ceiling** on usage not yet paid |
| 530 | for, and **your spend limit** on what is charged in a month. Work stops at |
| 531 | whichever is lower. Both are in the **Spend limit** section of **Settings → |
| 532 | Billing and plans**, on the plan. |
| 533 | |
| 534 | ### The ceiling |
| 535 | |
| 536 | Usage is charged after it runs, so at any moment some of it is not yet |
| 537 | paid. g1t lets that reach a ceiling that grows with your history: |
| 538 | |
| 539 | | | Ceiling on what is unpaid | |
| 540 | | ------------------------------------ | ------------------------------------------------------------------------------------------------ | |
| 541 | | **Free** | None to reach: a free workspace is never charged. The trial and g1t's pools pay for its compute. | |
| 542 | | **First month on the plan** | $100 | |
| 543 | | **Paid** | Twice what you have paid, never below $100, up to $1,000 | |
| 544 | | **Established**: three steady months | Three times your monthly spend, up to $10,000 | |
| 545 | | **Reviewed** | What g1t set with you | |
| 546 | |
| 547 | - A payment counts once it has **cleared for 7 days**, the time in which |
| 548 | most bad cards are caught. Credits g1t gives and payments in test mode |
| 549 | do not raise the ceiling. |
| 550 | - **Established** comes by itself after three months in a row of $20 or |
| 551 | more, every invoice paid, nothing declined in 90 days and nothing ever |
| 552 | disputed. |
| 553 | - **Prepaying** raises what can be used before work stops by the same |
| 554 | amount, at once. See [prepay](#prepay). |
| 555 | |
| 556 | With a card on file, **g1t charges it as you near the ceiling** (80%): an |
| 557 | invoice for what you owe, paid at once, after which the ceiling is yours |
| 558 | again. A workspace that pays keeps going; the ceiling stops one that does |
| 559 | not. |
| 560 | |
| 561 | What counts as unpaid is each item at what it cost g1t or what it is |
| 562 | charged, whichever is more, less what was paid this month, plus anything |
| 563 | left unpaid from earlier months. What included usage, the trial or the |
| 564 | open-source pool paid for does not count. |
| 565 | |
| 566 | ### Your spend limit |
| 567 | |
| 568 | What the workspace may be charged in a month (UTC): usage at price after |
| 569 | your discount, included usage, the trial, pools and credit, as |
| 570 | [How spend is counted](#how-spend-is-counted) defines it, the same figure |
| 571 | as the plan card's **charged**. At it, new work stops until the month |
| 572 | turns or an owner raises it. Until owners set one, it is |
| 573 | **automatic**: $200, or twice last month's spend, whichever is more, up to |
| 574 | what is available. |
| 575 | |
| 576 | Owners set it under **Your monthly spend limit**: **Automatic**, **Fixed |
| 577 | at** an amount, **Everything available**, or, once, **Use my one-time |
| 578 | raise**, then **Save limit**. The section says how far you can go yourself, |
| 579 | and whether the one-time raise is still yours: |
| 580 | |
| 581 | | | Up to | |
| 582 | | ------------------------------------------ | --------------------------------------------------------------- | |
| 583 | | Any amount | The highest ceiling the workspace has had, plus what is prepaid | |
| 584 | | **The one-time raise**, once per workspace | Twice the highest ceiling | |
| 585 | | Past that | **Raise my limit**: a request to g1t | |
| 586 | |
| 587 | To ask for more, use the **Raise my limit** section: give the limit you |
| 588 | need, what you expect to spend a month, and what it is for, then **Send the |
| 589 | request**. A person at g1t answers **within one business day**, in the app |
| 590 | and by email, and the section shows the request and its answer. An approved amount becomes a |
| 591 | floor under your ceiling, and your spend limit can go up to it. |
| 592 | |
| 593 | ### Budget alerts |
| 594 | |
| 595 | The spend limit is the workspace's monthly **budget** on usage past what the |
| 596 | plan includes. Under **Budget alerts**, owners choose: |
| 597 | |
| 598 | | Setting | Means | |
| 599 | | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
| 600 | | **Alert at** | Any of 50, 75, 90 and 100% of the spend limit. Each is emailed to the owners once a month. | |
| 601 | | **Pause usage at 100%** | On (the default), new work stops at the limit: workflows, checks, the merge queue, builds and deploys, until the month turns or an owner raises it. Work already running finishes, so spend can go slightly past it. Off, the budget only alerts; g1t's own ceiling still applies. | |
| 602 | | **Webhook** | An `https://` address of your own, sent a JSON `POST` at each alert: `event` (`budget.alert`), `workspace`, `level_percent`, `spent_micros`, `budget_micros`, `sent_at`. | |
| 603 | |
| 604 | Choose **Save alerts**. Through the API: `PUT /workspaces/:workspace/budget`, |
| 605 | or the MCP `billing` tool's `set_budget` action. |
| 606 | |
| 607 | ### Prepay |
| 608 | |
| 609 | Paying in advance pays for usage as it happens, after the plan's included |
| 610 | usage, and raises what can be used before work stops by the same amount, |
| 611 | at once. It is never needed to start work. Only an owner can prepay. |
| 612 | |
| 613 | 1. Open **Settings → Billing and plans**, and find **Prepay**. |
| 614 | 2. Choose **By card, with 3-D Secure** or **By bank transfer** (from |
| 615 | $1,000). |
| 616 | 3. Choose $100, $500 or $1,000, or type your own amount, from $25, and |
| 617 | choose **Prepay**. By card, the most is $10,000. |
| 618 | 4. Pay on the page you are sent to, confirming 3-D Secure if your bank |
| 619 | asks. A bank transfer page gives the account details, and the amount |
| 620 | counts when the money arrives. |
| 621 | |
| 622 | There is no fee on top, by card or by bank transfer. [Tax](#tax) is added |
| 623 | where it applies. What you prepay is credited in full: the tax does not |
| 624 | come from it. |
| 625 | |
| 626 | **Prepaid balance** shows what is paid in advance and not used yet. |
| 627 | |
| 628 | ### Alerts |
| 629 | |
| 630 | Owners are told at **50%, 75%, 90% and 100%** of each of: |
| 631 | |
| 632 | - the plan's included usage, |
| 633 | - your spend limit, |
| 634 | - g1t's ceiling. |
| 635 | |
| 636 | Each alert shows at the top of **Billing** and is emailed. |
| 637 | |
| 638 | ### Spikes |
| 639 | |
| 640 | If the last hour's spend is more than **5 times the workspace's usual |
| 641 | hour** over the last week, and at least **$5**, new compute pauses until an |
| 642 | owner answers. Runs already under way finish. A banner across the top of |
| 643 | every page in the workspace says so, and **Billing** shows the spike with |
| 644 | two choices, for owners on both: |
| 645 | |
| 646 | - **Keep going**: compute starts again, for 24 hours or until the hour's |
| 647 | spend doubles again, whichever comes first. |
| 648 | - **Stop**: compute stays paused until an owner chooses **Keep going**. |
| 649 | |
| 650 | g1t's own workspaces are never paused. |
| 651 | |
| 652 | ### Spent more than you meant to |
| 653 | |
| 654 | If a month went past what you meant to spend, use **Spent more than you |
| 655 | meant to? Tell us.** on **Billing**: say what happened and choose **Tell |
| 656 | g1t**. Once in 12 months per workspace, g1t can credit the overage above |
| 657 | your usual month: always the 20% g1t added to it, and what it cost g1t up |
| 658 | to $50. Larger credits, or a second one within 12 months, are reviewed by a |
| 659 | person. The credit appears on the statement with the day it happened, |
| 660 | such as _Credit from g1t: accidental usage on 2026-11-12_. |
| 661 | |
| 662 | ## Credits from g1t |
| 663 | |
| 664 | g1t sometimes adds credit to a workspace: a welcome or referral credit, an |
| 665 | apology, or a refund for something that went wrong. The workspace's owners |
| 666 | get an email when it does, and **Billing** shows a **Credits from g1t** |
| 667 | card with each credit in a line, such as _$25.00 credit, $12.40 left, |
| 668 | expires Jan 5_. |
| 669 | |
| 670 | | Kind | What it is | Expires | |
| 671 | | ----------- | -------------------------------------------------------------- | ---------------------------------------------------- | |
| 672 | | Promotional | A welcome, a referral or an event. | Sometimes: the date is on the card and in the email. | |
| 673 | | Goodwill | An apology, or usage past what you meant forgiven. | Sometimes, as above. | |
| 674 | | Refund | Money back for something that went wrong, with what it is for. | Never. | |
| 675 | |
| 676 | How credit is used: |
| 677 | |
| 678 | 1. It is added to your balance at once, so it lowers what you owe and |
| 679 | raises what you can use before work stops. |
| 680 | 2. Usage is paid from credit before anything you prepaid, and from the |
| 681 | credit that expires soonest first. |
| 682 | 3. Given while the workspace owes for this month, it pays that first. |
| 683 | 4. Credit left when it expires stops counting, and the statement shows a |
| 684 | line for what expired. g1t can also withdraw credit given by mistake; |
| 685 | only what is left is withdrawn, never what was already used. |
| 686 | |
| 687 | Credit is never paid out as money, and is never charged to a card. On the |
| 688 | statement, credits, expiries and withdrawals are under **Credits from g1t**. |
| 689 | |
| 690 | ## Invoices |
| 691 | |
| 692 | Every charge is a real invoice from g1t, kept on Stripe's billing page |
| 693 | with its PDF and emailed as a receipt: |
| 694 | |
| 695 | - **When each month closes**, an invoice for what the workspace owes, |
| 696 | itemised: the plan, usage past what it includes, and anything left |
| 697 | unpaid from before. Prepaid money is taken off as _Paid in advance_. |
| 698 | - **When the workspace nears its ceiling** mid-month, the same, sooner. |
| 699 | - **When the workspace is deleted**, a final invoice for what it owes, |
| 700 | charged at once with no minimum. See |
| 701 | [deleting a workspace](/guides/workspaces/#what-billing-needs). |
| 702 | |
| 703 | Each is charged to the card on file, with [tax](#tax) as a line of its |
| 704 | own and no card fee. On Stripe's payment page and on receipts, the plan is |
| 705 | named **g1t plan for _workspace_**, such as **g1t plan for acme**. Every invoice and receipt, with its PDF, is on |
| 706 | Stripe's billing page: choose **Manage billing** under **Billing on |
| 707 | Stripe**. |
| 708 | |
| 709 | ## Tax |
| 710 | |
| 711 | Every price on g1t excludes tax. Stripe adds sales tax, VAT or GST where it |
| 712 | applies (Stripe Tax), worked out from the workspace's billing address, and |
| 713 | shows it as its own line before you pay and on every receipt and invoice. |
| 714 | The plan, add-ons, prepaying and invoices are all taxed the same way, as software as a service for business use. |
| 715 | |
| 716 | - **The address.** Stripe's payment pages always ask for a billing |
| 717 | address, and save it on the workspace's Stripe customer. A card check |
| 718 | saves the card's billing address there too, if there is none yet. You |
| 719 | change it on Stripe's billing page: see [Your card and billing |
| 720 | details](#your-card-and-billing-details). |
| 721 | - **A business tax ID.** Add it on Stripe's payment page or on its billing |
| 722 | page (the kind, such as EU VAT, and the number). Stripe checks it and |
| 723 | applies it where the law says so, such as a reverse charge. |
| 724 | - **No address, no charge.** Where Stripe has nothing to work tax out |
| 725 | from, g1t does not charge the card. Billing shows **Add your billing |
| 726 | address in Stripe** with a **Manage billing** button, the owners are |
| 727 | emailed once, and the charge goes through once the address is saved. Nothing is lost, and work is not stopped for it. |
| 728 | In the United States the ZIP code is needed; elsewhere the country. |
| 729 | - **Tax exempt.** If your organisation is exempt, write to |
| 730 | support@g1t.sh with the certificate; Billing then says **Tax exempt**. |
| 731 | - **Refunds** give the tax back in proportion. |
| 732 | |
| 733 | Tax is never part of your balance or usage: the statement shows it as its |
| 734 | own line, beside the payment it came with. |
| 735 | |
| 736 | ## No card processing fee |
| 737 | |
| 738 | g1t's prices include what Stripe charges to take a card. Nothing is added |
| 739 | on top of the plan, a prepayment or an invoice, however you pay. Payments |
| 740 | from before the fee was folded into prices may show **Card processing |
| 741 | fees** on the statement; those stay as they were. |
| 742 | |
| 743 | ### The minimum charge |
| 744 | |
| 745 | Only the month's close has a minimum: a card is not charged less than |
| 746 | **$5** then, so a payment's processing cost is never most of what is paid. When a month |
| 747 | closes owing less, the amount carries over to the next invoice that reaches |
| 748 | $5, as _Unpaid from earlier_. A charge made because a workspace is at or |
| 749 | near a limit always goes through, whatever the amount, so work can carry |
| 750 | on. |
| 751 | |
| 752 | ## Moving a repository between workspaces |
| 753 | |
| 754 | When a repository is [transferred](/guides/transferring-repositories/#billing), |
| 755 | usage from that moment is charged to the workspace it moved to: workflow |
| 756 | jobs, builds, app traffic, git operations and storage. What it used before stays |
| 757 | on the old workspace's bill, and runs already under way finish on the bill |
| 758 | they started on. |
| 759 | |
| 760 | ## Your card and billing details |
| 761 | |
| 762 | Your card, billing address, tax IDs, invoices and receipts live on |
| 763 | **Stripe's billing page**, not on g1t: g1t never sees or stores card |
| 764 | numbers. On **Settings → Billing and plans**, owners and billing managers |
| 765 | see **Billing on Stripe**: |
| 766 | |
| 767 | - the default card (brand, last four digits and expiry), read-only; the |
| 768 | plan charges it. |
| 769 | - **Manage billing**, which opens Stripe's billing page. There you add, |
| 770 | remove or replace a card and make one the default; change the billing |
| 771 | email, name, address and phone; add or remove tax IDs; see and download |
| 772 | every invoice and receipt (the plan and month-end usage); and end the |
| 773 | plan at the end of the period, or keep it after all. [Tax](#tax) is |
| 774 | worked out from the address you keep there. |
| 775 | |
| 776 | **Add-ons** lists what comes with the plan, such as |
| 777 | [Security and quality](/guides/security/pricing/), and whether it is on. |
| 778 | |
| 779 | g1t support never takes card details by phone or email. |
| 780 | |
| 781 | If a card is declined, work stops until the workspace pays, and the |
| 782 | Billing page and the API say why. Replace the card under **Manage billing**, |
| 783 | or prepay, to clear it. |
| 784 | A payment disputed with the card's bank stops work the same way. |
| 785 | |
| 786 | Through the API, `GET /workspaces/:workspace/billing_details` and |
| 787 | `GET /workspaces/:workspace/invoices` (the MCP `billing` tool's |
| 788 | `billing_details` and `invoices` actions) read the same. |
| 789 | |
| 790 | ## When work is stopped |
| 791 | |
| 792 | A workspace that cannot start compute starts nothing new. Starting a |
| 793 | workflow, a merge queue run or a deploy is refused with `402` and a |
| 794 | message saying why and what to do, with the page to do it on: start the |
| 795 | plan, check a card, raise the spend limit, answer a spike, or wait for the |
| 796 | next month's pool. |
| 797 | |
| 798 | A workflow job is recorded as failed with "Not started:" and the reason. |
| 799 | Runs already under way finish, so usage can go slightly past a limit. |
| 800 | |
| 801 | ### When g1t pauses work for everyone |
| 802 | |
| 803 | If usage across all of g1t climbs far past normal, g1t can pause some |
| 804 | kinds of work for every workspace while it looks into it. Each pause is |
| 805 | separate, and runs already under way finish: |
| 806 | |
| 807 | | Paused | What you see | |
| 808 | | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | |
| 809 | | Compute | New checks, workflow jobs and deploy builds are refused with `paused` and a message that g1t has paused them across the platform. Try again later. | |
| 810 | | Schedules | Workflows on `schedule:` skip the minutes while it lasts; they are not run late. | |
| 811 | | Indexing | New semantic search embeddings wait. Text search still answers, and search keeps up with new pushes. | |
| 812 | | Renders | A link to g1t shows g1t's logo instead of the page's own card. | |
| 813 | |
| 814 | Nothing in your workspace changes, and nothing is charged while work |
| 815 | waits. |
| 816 | |
| 817 | ## Security on every plan |
| 818 | |
| 819 | Every workspace, free or on the plan, has the [audit log](/guides/audit-log/), |
| 820 | with the same CSV and JSON export, and secret scanning, push protection, |
| 821 | vulnerability alerts and security updates. The rest of the security suite |
| 822 | (custom patterns, validity checks, delegated bypass, code scanning, |
| 823 | dependency review and the security overview) is free on public |
| 824 | repositories and, on private ones, comes with the plan as **Security and |
| 825 | quality**, with no price of its own: its scans are charged at cost plus |
| 826 | 20%. See |
| 827 | [what's free and what's paid](/guides/security/pricing/). What the plan changes is how long the log is |
| 828 | kept: [7 days free, 90 on the plan](/guides/audit-log/#how-long-it-is-kept), |
| 829 | and longer by arrangement. Single sign-on through your identity provider is not |
| 830 | built yet; when it is, it will be on every plan. |
| 831 | |
| 832 | ## Enterprises and custom terms |
| 833 | |
| 834 | Some accounts are billed differently, set up by g1t with you. Every price |
| 835 | is public; custom terms change how you pay, not what things cost. |
| 836 | |
| 837 | - **Enterprise**: one billing account paying for several workspaces. |
| 838 | Their usage and payments count together, against one limit, and each |
| 839 | workspace's Billing page says which enterprise pays for it. An |
| 840 | enterprise is **invoiced**: when each month closes, one invoice goes to |
| 841 | the enterprise's billing address, with a line for each workspace, due in |
| 842 | 30 days and paid by card or bank transfer. If it goes overdue, the |
| 843 | workspaces' work stops until it is paid. [Tax](#tax) is added from the |
| 844 | enterprise's billing address, which g1t keeps on its Stripe customer, and |
| 845 | there is no card fee. |
| 846 | - **A discount**: a percentage off every usage charge, from a few percent |
| 847 | to 100%, with a reason, sometimes until a date. Prices themselves stay |
| 848 | the public ones. The statement shows every line at its price and the |
| 849 | discount beside it: the totals read **Usage at price**, **Discount |
| 850 | (30%)** and **Charged**, each day or project has a **Discount** line, and |
| 851 | the CSV has `price (USD)` and `discount (USD)` columns. The Usage page |
| 852 | shows usage at price too, with the discount and what was charged. |
| 853 | - **A 100% discount**: nothing is charged, and the plan is on without |
| 854 | being charged. The statement and the Usage page still show everything at |
| 855 | its price, so you can see what the workspace would pay. |
| 856 | - **A limit of its own**, or a larger share of the pools. |
| 857 | - **A longer audit log**: up to 400 days for every workspace the account |
| 858 | pays for, in place of the plan's 7 or 90. See |
| 859 | [how long it is kept](/guides/audit-log/#how-long-it-is-kept). |
| 860 | |
| 861 | g1t's own workspaces and those of Flagon, Inc., the company that makes g1t, |
| 862 | have a 100% discount. Their usage is shown at price and kept apart from |
| 863 | what customers pay. |
| 864 | |
| 865 | ### Complimentary terms |
| 866 | |
| 867 | g1t can enroll a workspace in **complimentary** terms, such as for a |
| 868 | design partner. A new workspace is never enrolled on its own: g1t staff |
| 869 | choose each one. An enrollment gives: |
| 870 | |
| 871 | - **The plan's features**, without the plan's $21 a month. |
| 872 | - **A monthly usage allowance**, such as $100. Usage counts against it at |
| 873 | its ordinary price, the same prices everyone pays: it is an amount of |
| 874 | usage g1t pays for, not a discount. It starts again on the 1st of each |
| 875 | month (UTC), and what is unused does not carry over. |
| 876 | - **A monthly fee of its own**, often none. When there is one, Stripe |
| 877 | invoices it each month, apart from the allowance. |
| 878 | |
| 879 | **Billing** has a **Complimentary allowance** card: the allowance a month |
| 880 | (or **Unlimited**), the monthly fee or **No monthly fee**, and **Used**, |
| 881 | **Metered, not billed yet**, **Remaining** and **Starts again**. Usage that is measured |
| 882 | at the end of the month, such as storage and git operations, and work |
| 883 | running now count against what is left. |
| 884 | |
| 885 | What happens at the allowance is part of the terms, and **Billing** says |
| 886 | which: |
| 887 | |
| 888 | - **New work that costs money stops** until the month turns: new runner |
| 889 | jobs, builds, deployments and other compute, and storage and caches past |
| 890 | the free amounts. Nothing is ever charged for usage past it, whether or |
| 891 | not a card is saved. Work already running when the allowance runs out |
| 892 | finishes, and g1t covers what it cost past the allowance. |
| 893 | - **Or usage past it is charged to your card**, such as when g1t covers a |
| 894 | set amount of an employee's or a friend's usage. Past the allowance, |
| 895 | usage is charged at the same prices as on the plan, up to your |
| 896 | [spend limit](#limits) and the [ceiling](#the-ceiling), and invoiced |
| 897 | when the month closes. Add a card first, with **Add a card** on the |
| 898 | allowance card: without one, work stops at the allowance until you do. |
| 899 | |
| 900 | If g1t changes the amount, what the month already used still counts: |
| 901 | raising it adds only the difference, and lowering it below what was used |
| 902 | leaves nothing more this month, never a bill. |
| 903 | |
| 904 | An owner or billing manager can choose **Start the g1t plan instead** on |
| 905 | the allowance card. The plan uses the same Stripe customer and |
| 906 | subscription, and nothing changes until its first payment goes through: |
| 907 | if the card is declined, the bank asks to confirm the payment, or the page |
| 908 | is closed, the complimentary terms stay as they were. Usage the allowance |
| 909 | paid for before the plan started is never charged afterwards. |
| 910 | |
| 911 | Each change is made by g1t staff and recorded with who made it and why. To |
| 912 | ask for one, write to [support@g1t.sh](mailto:support@g1t.sh). |
| 913 | |
| 914 | ## Earlier plans |
| 915 | |
| 916 | Deployments used to be a $5 plan of its own. It is part of the g1t plan |
| 917 | now. A Deployments subscription bought before keeps working until its |
| 918 | current period ends, and is not renewed. |
| 919 | |
| 920 | ## The Usage page |
| 921 | |
| 922 | A workspace's **Usage** page, `g1t.sh/<workspace>/-/usage`, shows what it |
| 923 | used, by product, project and day. Every member can see it, from **Usage** |
| 924 | in the workspace's sidebar. A project's own, `g1t.sh/<workspace>/<project>/usage`, |
| 925 | shows the same for that project. |
| 926 | |
| 927 | Every amount is **usage at price**: what was charged, plus what included |
| 928 | usage, credit or a discount paid for it. It is the one figure Usage and |
| 929 | Billing both show, so they agree. |
| 930 | |
| 931 | The filters, in one row: |
| 932 | |
| 933 | | Filter | Choices | |
| 934 | | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
| 935 | | Period | **Current billing cycle** (the calendar month, UTC), **Last billing cycle**, the last 7, 30 or 90 days, or a **Custom range** of up to 400 days. The days it covers are shown beside it. | |
| 936 | | Products | Any of Sandboxes, Deployments, Git & storage, Packages, Security & quality and Search. | |
| 937 | | Projects | Any of the projects with usage in the period. | |
| 938 | | Group by | Product, project or day, for the breakdown. | |
| 939 | | **⋯** | **Export CSV** (a row per day, product and meter) and the usage API. | |
| 940 | |
| 941 | Then: |
| 942 | |
| 943 | - **Included usage, credit and this range**: the plan's included usage this |
| 944 | month, credit from g1t left, and what the range came to: |
| 945 | usage at price, then the discount (shown as _Discount (100%)_ for a |
| 946 | workspace g1t covers in full), included usage and pools, credits applied, |
| 947 | and what is charged. |
| 948 | - **Consumption**: a column per day, week or month (**Daily**, **Weekly**, |
| 949 | **Monthly**), stacked by product, with **Cumulative** to add them up. |
| 950 | Hover or focus a column for each product's part; **Show as a table** has |
| 951 | every number. |
| 952 | - **The breakdown**: each product family with its meters (runner minutes |
| 953 | for each machine; |
| 954 | builds; git operations and private storage with what is free; and so |
| 955 | on), each with a trend line, how much was used and its charge at price. |
| 956 | Open a meter for its projects. |
| 957 | |
| 958 | Storage, git operations, scans and search embeddings are metered through |
| 959 | the month and charged when it closes; until then they are marked pending. |
| 960 | Through the API: `GET /workspaces/:workspace/usage`, or the MCP `billing` |
| 961 | tool's `usage` action. |
| 962 | |
| 963 | ## The statement |
| 964 | |
| 965 | The **Billing** page ends with the workspace's statement, a month at a |
| 966 | time. Every member can see it. |
| 967 | |
| 968 | - **Totals.** What the month charged, what was paid and credited, and how |
| 969 | many entries make it up. |
| 970 | - **Grouped by day or by project.** Each day (or project) has one line |
| 971 | per kind of charge, with how many entries it holds and what they come |
| 972 | to: |
| 973 | |
| 974 | | Line | What it holds | |
| 975 | | ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | |
| 976 | | Runner minutes, 2-core and Runner minutes, 4-core | Each job on g1t's machines, with the minutes charged on that machine. | |
| 977 | | Sandbox time | Each sandbox's time, in months before runner minutes. | |
| 978 | | Self-hosted runner time | Each job on your own runners, at $0. | |
| 979 | | Deployments | Builds as they finish; each month's requests, CPU time, custom domains and container time when it closes. | |
| 980 | | Private storage | Storage past the free 1 GB, once a month. | |
| 981 | | Actions cache storage | What `actions/cache` and artifacts held, on the plan, once a month. | |
| 982 | | Git operations | Operations past the free 50,000, once a month. | |
| 983 | | Search embeddings | Private text put in the search index, once a month. | |
| 984 | | Security scans | History scans and dependency checks, once a month. | |
| 985 | | Payments | Card payments and invoices paid. | |
| 986 | | Credits from g1t | Credit g1t added (promotional, goodwill or a refund), and what of it expired or was withdrawn. See [Credits from g1t](#credits-from-g1t). | |
| 987 | | Refunds | Money given back to your card. | |
| 988 | | Tax | Tax paid with that day's payments. Not a charge, and not from your balance. | |
| 989 | | Card processing fees | Only on payments from before the card fee was folded into prices: the fee paid with them. Not a charge, and not from your balance. | |
| 990 | |
| 991 | Payments are what reached your balance; the tax paid with them is the |
| 992 | line below them, and the totals say what it came to. |
| 993 | |
| 994 | - **Covered.** Below the totals, what paid for usage before it was |
| 995 | charged, each with its amount: |
| 996 | |
| 997 | | Line | What paid | |
| 998 | | ---------------------------------- | ------------------------------------------------- | |
| 999 | | Paid by your plan's included usage | The plan's $10 a month. | |
| 1000 | | Paid by your trial credit | The one-time trial. | |
| 1001 | | Paid by g1t's open-source pool | The pool, for public repositories. | |
| 1002 | | Covered by g1t | A free workspace's last trial run past its trial. | |
| 1003 | |
| 1004 | Each entry says in its description how much of it was paid this way. A |
| 1005 | month that closed under the [minimum charge](#the-minimum-charge) says |
| 1006 | what carried over. |
| 1007 | |
| 1008 | - **Open a line** to see its entries, 50 at a time, newest first. |
| 1009 | - **Pick a month** to see an earlier one. |
| 1010 | - **CSV** downloads every entry of the month, with the line it falls under |
| 1011 | and what covered it, for your own books. Invoices from Stripe remain the |
| 1012 | record for what was charged to your card. |
| 1013 | |
| 1014 | ## Provider cost reports |
| 1015 | |
| 1016 | g1t counts what its own runs cost. Your team's other agents (CI scripts, |
| 1017 | other tools, people's own sessions) are on your AI provider's bill too, |
| 1018 | and the provider's own cost report is the record of all of it. Connect |
| 1019 | the provider and g1t reads that report, day by day, at |
| 1020 | `g1t.sh/<workspace>/-/provider-costs` (**Provider costs**, under Money in |
| 1021 | the workspace's settings). |
| 1022 | |
| 1023 | **What it reads.** The provider's cost report for the whole organization |
| 1024 | the key belongs to, in US dollars, one line per day and line item: |
| 1025 | |
| 1026 | | Provider | Report | Line items | |
| 1027 | | --------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | |
| 1028 | | Anthropic | The Usage and Cost Admin API's cost report (`/v1/organizations/cost_report`) | Each description, such as _Claude Opus 5.5 Usage - Input Tokens_, for each of the organization's Console workspaces | |
| 1029 | | OpenAI | The Costs API (`/v1/organization/costs`) | Each line item, for each of the organization's projects | |
| 1030 | |
| 1031 | **Which key.** An admin key, which only an organization's admins can make: |
| 1032 | |
| 1033 | - **Anthropic**: an Admin API key (it starts `sk-ant-admin`), made in the |
| 1034 | Claude Console under **Settings**, **Admin keys**. An ordinary API key |
| 1035 | or a workspace's key can't read the cost report. Individual accounts have |
| 1036 | no Admin API: set up an organization first. |
| 1037 | - **OpenAI**: an admin key (it starts `sk-admin-`), made in the OpenAI |
| 1038 | platform under **Organization settings**, **Admin keys**. A project or |
| 1039 | user API key can't read the Costs API. |
| 1040 | |
| 1041 | Only an owner of the workspace can connect a provider, one key per |
| 1042 | provider. g1t checks the key with one small report request and says why |
| 1043 | when it doesn't work (the wrong kind of key, no permission), then reads |
| 1044 | the last 90 days. |
| 1045 | |
| 1046 | **What g1t keeps.** The key, sealed when it is saved; it is never shown |
| 1047 | again, never sent back to anyone and never written to a log. The page shows |
| 1048 | its last four characters, who connected it and when, when it was last read |
| 1049 | and what went wrong. And the costs: day, provider, line item, the provider's |
| 1050 | own workspace or project, and the amount. g1t uses the key for nothing but |
| 1051 | reading the report: never to run a model. |
| 1052 | |
| 1053 | **How often.** Once a day, around 04:17 UTC. Each read asks for the last |
| 1054 | seven days again, since providers revise recent days (and further back, |
| 1055 | up to 90 days, after reads have failed), and replaces what it had for |
| 1056 | those days. A provider that fails keeps its error on the page until a |
| 1057 | read works; the others are read as usual. The day in progress is |
| 1058 | incomplete at the provider too. |
| 1059 | |
| 1060 | **Not added to g1t's own figures.** Runs g1t made on the workspace's own |
| 1061 | key, such as Ask and sessions on [your AI providers](/guides/ai/), are on |
| 1062 | the provider's report as well. The provider's figure already includes |
| 1063 | them, so it is shown beside g1t's, never added to it. |
| 1064 | |
| 1065 | **Disconnecting.** **Disconnect** on the page deletes the key and every cost |
| 1066 | read with it. Replacing the key does the same and reads the last 90 days |
| 1067 | again, since a new key may belong to another organization. To stop the key |
| 1068 | working anywhere, also delete it at the provider. |
| 1069 | |
| 1070 | Members can see which providers are connected and what they reported; |
| 1071 | only owners connect, replace and disconnect them. Services read the figures |
| 1072 | with the billing service's `provider_costs` RPC. |
| 1073 | |
| 1074 | ## For services: entitlements, reserve, settle |
| 1075 | |
| 1076 | Every g1t service that starts something that costs money asks billing |
| 1077 | first. These RPCs are internal; they are documented so the behavior above |
| 1078 | can be traced. |
| 1079 | |
| 1080 | | RPC | Takes | Returns | |
| 1081 | | -------------- | ------------------------------------------------------- | -------------------------------------------------------------------------- | |
| 1082 | | `entitlements` | `workspace` | What the workspace may do now (below). | |
| 1083 | | `reserve` | `workspace`, `repo`, `public`, `kind`, `estimateMicros` | A reservation, or a refusal. | |
| 1084 | | `settle` | `reservationId`, `actualMicros` | `true`, or `false` if it was settled or had lapsed before. Safe to repeat. | |
| 1085 | |
| 1086 | **`entitlements`** returns, among others: `plan` (`free`, `paid`, |
| 1087 | `internal` or `enterprise`), `compute` (may start compute at all), |
| 1088 | `trialMicrosLeft`, `trialVerified` (a card check is done), `firstMonth`, |
| 1089 | `ceilingMicros`, `exposureMicros`, `heldMicros`, `prepaidMicros`, |
| 1090 | `includedMicros`, `includedUsedMicros`, `paused` (why compute is paused, |
| 1091 | or none), `spike`, `alerts`, `gitOperations` and `gitOperationsIncluded` |
| 1092 | (the git operations free for every workspace), `freePrivateStorageBytes` |
| 1093 | (the private storage free for every workspace) and `buildSecondsUsed`. |
| 1094 | None of these is a quota on the plan. |
| 1095 | |
| 1096 | **`usage_meters`** (`workspace`, `viewer`; members only) returns this |
| 1097 | month's usage in five lines, `builds`, `requests`, `domains`, |
| 1098 | `git_storage` and `search_scans`, each with `micros` (at cost plus 20%, |
| 1099 | before included usage or a pool paid for it) and a `quantity` such as |
| 1100 | _42 build minutes_, each at price (what was charged plus what paid for it), as Usage measures it. |
| 1101 | |
| 1102 | **`usage_report`** (`workspace`, `viewer`, `from`, `until`, optional `products` and `projects`; members only) is what the Usage page reads: totals (`priceMicros`, `discountMicros`, `includedMicros`, `creditsMicros`, `chargedMicros`, `pendingMicros`, `pendingChargedMicros`), each day's usage by product, and every product family with its meters, their daily figures and their projects. |
| 1103 | |
| 1104 | **`reserve`** holds the work's estimated cost before it starts, so starts |
| 1105 | at the same moment cannot overshoot together. `kind` is `check`, |
| 1106 | `workflow`, `queue`, `deploy` or `embedding`. `estimateMicros` is the most |
| 1107 | the work is expected to cost g1t **in millionths of a dollar, before the |
| 1108 | margin**; billing adds the margin. |
| 1109 | |
| 1110 | A reservation has an `id`, `paidBy` (`credit` for included usage, `trial`, |
| 1111 | `oss` or `on_demand`), `heldMicros` and `expiresAt`. A hold never settled |
| 1112 | **lapses after 3 hours**. A refusal has one of these codes and a message |
| 1113 | for the owner with the page to fix it on: |
| 1114 | |
| 1115 | | Code | Why | |
| 1116 | | ---------------- | --------------------------------------------------------------------------- | |
| 1117 | | `not_paid` | No plan, and nothing else pays for this kind of work, or no card check yet. | |
| 1118 | | `trial_used` | The one-time trial is spent. | |
| 1119 | | `limit` | The spend limit or g1t's ceiling would be passed. | |
| 1120 | | `paused` | A spend spike is waiting for an owner, or g1t staff put a hold on compute. | |
| 1121 | | `oss_pool_empty` | The open-source pool, or the repository's share of it, is spent this month. | |
| 1122 | |
| 1123 | **`settle`** releases the hold with what the work cost, at cost before the |
| 1124 | margin. It never charges: the charge goes on the ledger the usual way when |
| 1125 | the work reports its usage. |