Billing & Plans
This guide covers Conduit’s subscription billing — what your organization pays for Conduit and how that subscription is managed.
Pricing
Section titled “Pricing”Conduit is one flat plan — everything included. There are no feature tiers, no usage credits, and no per-call metering. You pay one predictable per-seat price and get the whole platform.
| Conduit | |
|---|---|
| Base organization fee | None — removed |
| Agent seats | 2 included; $39 / additional agent seat / month |
| Human seats | $39 / seat / month |
| What’s included | Everything — every feature, no gates |
Everything in the platform is included at the flat price:
- Unlimited vendor connections — connect as many of the vendor integrations as you need.
- Unlimited members and full team features (teams, roles, invitations).
- Role-based access — per-vendor, per-role scoping of which tools each role can call.
- Full audit — a clear record of every tool call, with CSV export.
- Log shipping to your SIEM (Loki, Graylog, LogScale).
- Prompt capture, SSO, and service clients (M2M) for automation.
No per-tier feature gating, no monthly credit allocation, and no per-call rate metering — the capabilities above are all on from day one. You are billed $39 for each agent seat beyond the two included and each human seat in the organization — there is no separate organization base fee.
Starting your subscription
Section titled “Starting your subscription”Every new organization starts on a free 14-day trial of the full platform automatically — there is no separate activation step. Hosted signup asks for a card; you get the full platform for 14 days at no charge, and you can cancel any time from your account settings. Manage the card on file and the subscription from the billing page at /org/billing.
Conduit never stores card data — only the Stripe customer ID and subscription state. See Security § Billing & Payment Security for how the payment integration is secured.
Managing a subscription
Section titled “Managing a subscription”From /org/billing, the owner or a member with the billing role (see Permissions § Org-member roles) can open the Stripe Customer Portal — Stripe’s hosted surface for updating the card on file, viewing invoices, adjusting seats, and cancelling. Conduit creates a portal session and redirects to it.
Invoice recipient
Section titled “Invoice recipient”By default, invoices and billing notifications go to the organization owner’s email. To send them somewhere else instead — a shared billing inbox, an office manager, an external bookkeeper — set an invoice recipient from /org/billing. This address is used for Conduit’s own billing lifecycle mail (trial and dunning notices) as well as Stripe invoices; it does not need to belong to a member of the organization.
Once set, the recipient can be changed to a different address at any time, but it cannot be emptied — to send invoices back to the owner, enter the owner’s address explicitly.
If the people who need this changed cannot reach the billing page themselves — an accounts payable team is the usual case, since they are rarely org members — contact support and we can set it for you.
When a payment fails — the dunning lifecycle
Section titled “When a payment fails — the dunning lifecycle”If a subscription renewal fails (expired card, insufficient funds), the organization moves through a dunning lifecycle rather than being cut off immediately. The lifecycle is designed so a billing hiccup does not instantly break your organization’s operations.
The states, in order:
| State | When | What the customer sees |
|---|---|---|
| Payment failing | First failure, within ~24h | A warning banner; full access retained while Stripe retries |
| Past due | 24h – 7d after first failure | A more prominent warning; full access still retained |
| Final warning | Inside the WYRE grace window, approaching its end | An urgent banner; full access still retained |
| Suspended | Grace window expired, or the subscription is canceled | Platform access is gated |
While in any pre-suspension state, the organization keeps full access — the grace window exists precisely so a failed renewal does not interrupt service. Once the grace window expires, the platform is gated at the service layer until payment is recovered.
The grace window
Section titled “The grace window”The grace window defaults to 7 days and is configurable per deployment via the WYRE_DUNNING_GRACE_DAYS environment variable. The first-failure timestamp is persisted, so the lifecycle survives service restarts and resumes from the correct point.
Recovery
Section titled “Recovery”When a failed payment is recovered (the customer updates their card and Stripe successfully charges it), the organization returns to normal. A recently-recovered org briefly shows a “recovered” confirmation, then returns to the standard no-banner state.
Cancellation
Section titled “Cancellation”Cancelling a subscription through the Stripe Customer Portal ends the subscription at the end of the current billing period. After that, the organization’s platform access is suspended — the data is preserved per the dunning model, so the organization can resume by re-subscribing.
Frequently asked questions
Section titled “Frequently asked questions”How is Conduit priced?
Section titled “How is Conduit priced?”Conduit is one flat plan — everything is included. There are no feature tiers, no usage credits, and no per-call metering. You pay a per-seat price, and every feature is on from day one.
What does a Conduit subscription cost?
Section titled “What does a Conduit subscription cost?”$39 per month for each human seat and for each agent (service-client) seat beyond the two included free — there is no separate organization base fee. The price is the same for every organization; a self-hosted deployment can override pricing via the PLAN_CATALOG environment variable.
How do I start — is there a trial?
Section titled “How do I start — is there a trial?”Yes. Every organization starts on a free 14-day trial of the full platform automatically. Hosted signup asks for a card; there is no charge during the trial, and you can cancel any time from your account settings. Self-hosted deployments can skip the card field.
What happens if a payment fails?
Section titled “What happens if a payment fails?”The organization moves through a dunning lifecycle rather than being cut off immediately — the payment-failing, past-due, and final-warning states all keep full access while a configurable grace window (7 days by default) runs. Only after the grace window expires is platform access gated, and recovering the payment restores it.
What happens if I cancel?
Section titled “What happens if I cancel?”Cancelling through the Stripe Customer Portal ends the subscription at the end of the current billing period, after which platform access is suspended. Your data is preserved, so the organization can resume by re-subscribing.