Plans and billing

Your plan belongs to the team, not to you. Every account starts with its own personal team, so even working alone you are on a team and that team carries the plan. Upgrading lifts the limits and turns on the paid features for everyone in it.

Self-serve billing has to be switched on for the dagweave instance you are using. When it is off the billing section does not appear at all.

Who can buy

Only a team owner can start a checkout or open the billing portal. Admins, editors and viewers cannot, and the billing section says so rather than failing on the attempt. If you are an admin who needs to pay, ask an owner or have them make you one.

Billing acts on your active team, the one that scopes your workspace. If you belong to several teams, switch to the one you want to pay for before you upgrade.

Upgrading

Open Team settings from the top bar and scroll to the billing section. It shows the team’s current plan, a choice of annual or monthly, and a row for each paid plan. The row matching your current plan is marked and its button is disabled.

Press the button on the row you want. On a team that has never subscribed it says Choose this, and dagweave hands you off to Stripe’s hosted checkout page. On a team that already has a subscription it says Change to this, and you go to the billing portal instead. The two are different places on purpose. A checkout only ever opens a new subscription, so changing one that already exists is the portal’s job, and the portal is the only surface that shows you the price of the change first. Card details go to Stripe. dagweave never sees them. Whether you finish or back out, Stripe returns you to dagweave.

The plan does not change the moment you land back. Stripe confirms the subscription to dagweave separately, and the team’s plan flips then. Reload if the new plan has not appeared yet.

Managing an existing subscription

Manage billing opens the Stripe billing portal for the team. From there you can change plan, update the card, and cancel. It needs a subscription to manage, so before the team’s first checkout it reports that there is none yet.

Cancelling drops the team to the unpaid plan once the subscription ends. That plan cannot dispatch runs, so a cancelled team keeps its workflows and its YAML but stops running anything on your cluster.

A failed payment does not change the plan by itself. Stripe retries on its own schedule, and the plan only moves if the subscription is eventually changed or ended.

What changes with the plan

Feature gates read the team’s plan on every request, so a change takes effect across dagweave at once. When you are over a limit the app says which one: the workflow limit for your plan, the monthly execution quota, or a feature the plan does not include.

Every plan change is written to the team’s audit log as a billing change, recording both the old plan and the new one.