A concurrent network is a workflow actively running at the same time as other workflows in the same workspace. Concurrency limits determine parallel run capacity, not total saved workflows.

Yes. NodeFox is in beta across plans. Capabilities, limits, and packaging may evolve, so teams should validate critical flows and monitor release notes before scaling high-impact usage.

The free-trial flow is intended for evaluation. During activation, users acknowledge trial terms, beta constraints, and billing behavior. If a trial converts to paid access, recurring billing follows the selected plan unless canceled before renewal.

For paid subscriptions, billing is processed through Stripe. NodeFox receives billing metadata needed for invoicing and subscription operations, while full payment card details are handled by Stripe.

Yes. You can cancel before the next renewal cycle to stop future billing. Cancellation timing, continued access windows, and refund handling follow your active terms and policy documents.

Teams can move between plans as needs evolve. Upgrades and downgrades follow active billing-cycle behavior and plan entitlements. Validate concurrency and workflow needs before changing tiers.

Before plan changes, review active runs, automations, and feature dependencies. Export critical workflows and logs if needed. Access behavior after cancellation depends on plan/policy terms.

Yes. Keep billing and backup contact details current so trial reminders, renewal events, and payment notices reach the right owners.

Annual and enterprise purchasing options are available through sales for teams that prefer consolidated procurement and contracting.

Plan limits are primarily based on concurrency and capability tiers rather than hidden per-run fees. Contact sales for high-volume usage design and contract planning.

Yes. Most teams start with one workflow family, validate deterministic behavior and controls, then expand coverage by department once reliability and governance patterns are proven.

Consent and opt-out workflows route to privacy@nodefox.ai. For policy interpretation use legal@nodefox.ai, for billing operations use billing@nodefox.ai, and for general routing use info@nodefox.ai.

Yes, with workspace organization and ownership boundaries that align to your operating model. Assign clear ownership for billing, approvals, and deployment decisions.

Yes. Enterprise contracting and rollout planning are supported through the enterprise page, including architecture-fit review, governance planning, procurement coordination, and phased implementation design.

Choose Automate for most team-scale production workloads. Choose Pro when concurrency, operational throughput, governance demands, or support requirements are substantially higher.