Stack Internal Plans and Billing

Plan Comparison

Capability	Starter	Organization
Price model	Free	Paid and quote based
Monthly Flow Credits	1,000	Starting at 15k Credits
Workspace members	Up to 3	Unlimited
Scopes	Up to 2 per workspace	Unlimited
Source connectors	Up to 3 connector types	Unlimited
Single sign on	Not included	Included
Custom roles	Cannot create or configure	Included for people and agents
Audit logs	Not included	Included

Organization credit bands start at 15,000 flow credits with additional tiers available. A custom enterprise agreement and an optional 10,000-credit monthly add-on are also available through Sales.

A connector type is counted separately from the number of accounts or workspaces connected through it. For example, Google and Slack are different connector types. Stack Internal Community also counts when it is enabled. Confirm connector-counting details with your account team when planning a Starter workspace.

How Flow Credits Work

Flow Credits measure active use. Connector ingestion is not metered under the current model, and people, teams, and integrated systems can be onboarded without per-seat charges. Credits are used when Stack Internal returns knowledge or changes knowledge or another system.

Flow type	Credit use	Examples
Access Flow	1 credit	Search, lookup, conversational synthesis, and trust or accuracy checks that do not change system state
Input Flow	3 credits	Knowledge additions and revisions, graph updates, writebacks, and completed automated actions
Connector ingestion	Unmetered	Importing knowledge through supported connectors under the current pricing model

Access Flows (reads & context summary) - 1 credit per Flow

• Definition An interface, custom developer API connector, or autonomous agent pipeline retrieves verified context or data without altering the state of your underlying knowledge repository.
• Core Rule You ask a question or initiate a query, and the platform returns an answer or data. The internal knowledge base, graph, and external systems remain completely unchanged.
• Included Activities Point-to-point text lookups, global semantic workspace searches, complex multi-source conversational chat synthesis, and premium verification features (including real-time confidence scores, text decay monitoring, and source contradiction flagging).
• Credit value Each Access Flow consumes one Flow Credit toward your monthly allotment.

Input Flows (writes & actions) - 3 credits per Flow

• Definition The platform actively alters a state, executes a write, or performs a transaction within your repository, graph, or an external system.
• Core Rule The platform actively executes a task or a change occurs inside your system or graph structure.
• Included Activities Automated node creation, graph memory updates, codebase merges, cross-system writebacks, and multi-step background tool loops executed run-to-completion.
• Credit Value Due to the higher operational layer of task delegation, each Input Flow consumes three Flow Credits toward your monthly allotment.

Protective usage thresholds may apply to unusually large or abusive ingestion patterns even when ingestion is not billed as a Flow.

Monthly allocation and reset behavior

Credits reset at the beginning of each plan usage period. Unused credits expire and do not roll into a later period. Starter is intended to refresh on a calendar-month cadence. Organization usage periods align to the paid subscription and billing schedule stated in the customer order form.

Because metering updates are event based, a workspace may briefly pass its displayed balance before the latest activity reaches the usage ledger. The plan cap still governs the next metered action after exhaustion is recognized.

Usage warnings and zero credit behavior

Usage point	What customers should expect
100 percent on Starter	Metered requests and Input Flows are blocked. The person sees an upgrade message; users without purchasing authority are directed to a workspace administrator.
100 percent on Organization	Service continues under the soft cap. The first exhaustion event prompts account-team follow-up about right-sizing the monthly allocation.

Persistent Organization usage above the contracted allocation may require a higher band and may ultimately lead to a hard cap under the customer agreement. Exceeding usage may require moving up additional tiers.

Custom roles and other enterprise controls

Organization includes single sign-on, custom roles with granular permissions for people and agents, and audit logs. Starter does not include these controls.

Purchasing and upgrade paths

Starter can be created without a payment method. Current Organization purchases and plan changes are handled through Sales. Your account team will confirm the monthly credit band, annual commitment, price, effective date, and order terms.

To increase capacity, you can move to a higher Organization band, and discuss a custom enterprise agreement. Starter top-ups are not available as an initial self-service purchase; contact Sales to move to Organization or request more capacity.

Changing spend or tier

Ask your account team to change your credit band, add capacity, upgrade, downgrade, or cancel. Organization uses an annual commitment in the current model.

Payment methods invoices and taxes

For an Organization purchase, the order form establishes the payment method, billing frequency, invoice recipient, due dates, currency, and tax treatment. The current product does not provide a universal self-service billing portal.

For invoice copies, purchase-order updates, billing-contact changes, tax questions, or exemption documentation, open a request through Stack Internal Support. Your customer agreement and order form control if they differ from this guide.

Upgrades and cancellation

Upgrades and capacity increases are coordinated with the account team so the new allocation and commercial terms can be confirmed. Their effective date, renewal treatment, and any notice requirement follow the active order form. Do not assume that canceling automatically converts an Organization workspace to Starter; confirm the intended workspace state in the request.

Failed payment handling

For current Organization agreements, late or failed payment handling follows the invoice and customer agreement. Contact the account team or Stack Internal Support promptly if a payment cannot be completed or an invoice is disputed.

Contact paths

Start upgrades Starter plans that want to upgrade to a paid tier can contact our sales team.

Sales and plan changes Contact your sales team for pricing, purchases, credit bands, upgrades, downgrades, cancellation, and contract changes.

Product and billing support Stack Internal Support can help with invoices, payment questions, tax documentation, usage reporting, and entitlement behavior.