flagon-io/g1t

public

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

git agents cloudflare rust forge mcp

Commit

Billing's docs say g1t.sh takes live payments, how the plan's card reads its usage month and renewal, that a month's git operations are charged in full, and Actions says how many jobs a workspace runs at once (#52).

Limitations still said g1t.sh might charge no real card "before its live payments are switched on"; payments are live, so only a g1t set up with Stripe test keys charges no real card. The plan's card on Billing now reads "Usage month Oct 1 – Oct 31, 2026; the plan renews Nov 15, 2026", and the guide says why the two differ (usage by calendar month, renewal on the day the plan started). Invoices says Stripe's page and receipts name the plan "g1t plan for <workspace>". Git operations says a month is charged and closed only after its final count, taken once the month has ended, so its last hours are charged too. Complimentary terms use the allowance card's labels: Complimentary allowance, Used, Metered, not billed yet, Remaining, Starts again, Add a card and Start the g1t plan instead. Actions' machine sizes say a workspace always has room for 4 jobs at once on g1t's machines and up to 12 while the pool has room, self-hosted jobs aside; no guide carried the old 4-only figure.

Checked:: the plan card's text and endsOn's date format in apps/web/app/components/billing-settings.tsx (PlanSummary, ComplimentaryCard), plan_line_name in services/billing/src/stripe.rs, the month-end count in 4ea0da72 (services/billing/src/storage.rs, invoices.rs), RUNNING_PER_WORKSPACE, BURST_PER_WORKSPACE, POOL_HEADROOM and has_room in services/actions/src/lib.rs and start_queued in plan.rs (hosted jobs only, oldest first). That g1t.sh's Stripe key is live is not in the code (is_live reads the secret); it rests on the live cutover recorded for #47. The docs build passes.
G1t-Session:: ses_01m4ynr1peevvs8zwaqakycv2e

syntaqxcommitted yesterdayParent3819d99Browse files

183	183		once. Otherwise, pay on the card page you are sent to.
184	184
185	185		Back on Billing, the plan's card says On the g1t plan (first month
186		−	in the first billing cycle), with the billing period, a meter for the
187		−	month's included usage, and the Upcoming invoice: the plan and add-ons
	186	+	in the first billing cycle), with the usage month and the day the plan
	187	+	renews: Usage month Oct 1 – Oct 31, 2026; the plan renews Nov 15, 2026.
	188	+	Usage is counted by calendar month (UTC), but the plan renews on the day
	189	+	of the month it started, so a plan started mid-month renews mid-month.
	190	+	Then come a meter for the month's included usage, and the Upcoming invoice: the plan and add-ons
188	191		at their monthly price plus usage still owed after included usage, credit
189	192		and any discount, from g1t's own ledger (View upcoming invoice splits
190	193		it). Usage goes to usage by product and project. App traffic, custom
⋯
435	438		Charging starts on 2026-10-14: operations before then are never charged.
436	439		Billing shows this month's count under Git operations & storage.
437	440
	441	+	A month's operations are charged in full, up to its last minute: its
	442	+	final count is taken once the month has ended (from an hour after
	443	+	midnight UTC on the 1st), and the month is charged and closed only after
	444	+	that, at the plan the workspace had that month.
	445	+
438	446		## Storage, search embeddings and scans
439	447
440	448		These are counted through the month and charged once it is over, as one
⋯
687	695		[deleting a workspace](/guides/workspaces/#what-billing-needs).
688	696
689	697		Each is charged to the card on file, with [tax](#tax) as a line of its
690		−	own and no card fee. Every invoice and receipt, with its PDF, is on
	698	+	own and no card fee. On Stripe's payment page and on receipts, the plan is
	699	+	named *g1t plan for workspace*, such as g1t plan for acme**. Every invoice and receipt, with its PDF, is on
691	700		Stripe's billing page: choose Manage billing under **Billing on
692	701		Stripe**.
693	702
⋯
861	870		- A monthly fee of its own, often none. When there is one, Stripe
862	871		invoices it each month, apart from the allowance.
863	872
864		−	Billing shows the allowance, what is used, what is metered but not
865		−	billed yet, what is left, and when it starts again. Usage that is measured
	873	+	Billing has a Complimentary allowance card: the allowance a month
	874	+	(or Unlimited), the monthly fee or No monthly fee, and Used,
	875	+	Metered, not billed yet, Remaining and Starts again. Usage that is measured
866	876		at the end of the month, such as storage and git operations, and work
867	877		running now count against what is left.
868	878
⋯
878	888		set amount of an employee's or a friend's usage. Past the allowance,
879	889		usage is charged at the same prices as on the plan, up to your
880	890		[spend limit](#limits) and the [ceiling](#the-ceiling), and invoiced
881		−	when the month closes. Add a card on Billing first: without one,
882		−	work stops at the allowance until you do.
	891	+	when the month closes. Add a card first, with Add a card on the
	892	+	allowance card: without one, work stops at the allowance until you do.
883	893
884	894		If g1t changes the amount, what the month already used still counts:
885	895		raising it adds only the difference, and lowering it below what was used
886	896		leaves nothing more this month, never a bill.
887	897
888		−	An owner or billing manager can start the g1t plan instead from the
889		−	allowance card on Billing. The plan uses the same Stripe customer and
	898	+	An owner or billing manager can choose Start the g1t plan instead on
	899	+	the allowance card. The plan uses the same Stripe customer and
890	900		subscription, and nothing changes until its first payment goes through:
891	901		if the card is declined, the bank asks to confirm the payment, or the page
892	902		is closed, the complimentary terms stay as they were. Usage the allowance

464	464		### Payments in test mode
465	465
466	466		A g1t whose payments use Stripe's test mode, such as a self-hosted one set
467		−	up with test keys, or g1t.sh before its live payments are switched on,
468		−	charges no real card, so a card check there proves nothing. With live
469		−	payments, the card check and every charge are real. Status. By design
	467	+	up with test keys, charges no real card, so a card check there proves
	468	+	nothing. g1t.sh takes live payments: the card check and every charge are
	469	+	real. Status. By design
470	470		for test setups.
471	471
472	472		## Accounts, status and self-hosting

572	572		as `ubuntu-24.04-arm`, runs on x64, and the workflow's page says so; a
573	573		self-hosted Arm runner runs it on Arm.
574	574
	575	+	A workspace always has room for 4 jobs at once on g1t's machines, and runs
	576	+	up to 12 at once while the machines have room to spare; the rest stay queued,
	577	+	oldest first, and start as others finish. Some machines are always kept free,
	578	+	so another workspace's first jobs start at once. Jobs on
	579	+	[self-hosted runners](/guides/self-hosted-runners/) do not count toward
	580	+	this.
	581	+
575	582		### What a job can reach
576	583
577	584		A job reaches the internet, as on GitHub's machines: package registries,

flagon-io/g1t

Billing's docs say g1t.sh takes live payments, how the plan's card reads its usage month and renewal, that a month's git operations are charged in full, and Actions says how many jobs a workspace runs at once (#52).

Comments