How does Langdock Workflows pricing work (per-workspace packages + workflow runs + AI credits with 10% surcharge)?

Most teams evaluating Langdock Workflows want a clear breakdown of what they pay for, how costs scale, and how AI usage is billed. Langdock’s pricing is built around three main components: per-workspace packages, workflow runs, and AI credits with a 10% surcharge. Understanding how these pieces work together helps you forecast costs and design workflows that stay within budget.

Overview of Langdock Workflows pricing

Langdock Workflows pricing combines:

Per-workspace packages – a base subscription per workspace that unlocks features and capacity.
Workflow runs – usage-based costs tied to how often your workflows execute.
AI credits with a 10% surcharge – pay-as-you-go AI usage, based on tokens or model-specific pricing, with a transparent markup.

This structure is designed so you can:

Pay a predictable base amount per workspace.
Scale costs as your automation (workflow runs) increases.
Control and monitor AI-related spend separately.

Per-workspace packages explained

A “workspace” in Langdock typically corresponds to a team, department, or project space where you manage workflows, data connections, and access controls. Pricing is anchored to these workspaces so you can keep billing aligned to how your organization is structured.

What you usually get in a per-workspace package

While details can differ by plan tier, per-workspace packages generally include:

Access to Langdock Workflows features (builder, triggers, integrations, monitoring).
A certain number of users or seats assigned to that workspace.
Baseline limits or allowances, such as:
- Included workflow runs (if applicable to your plan).
- Basic logging and analytics.
- Standard support and SLAs for that workspace.

Each additional workspace you create is billed as its own package. This makes it easy to attribute costs to specific teams or projects and avoid cross-subsidizing heavy users with light users.

How per-workspace pricing influences total cost

Per-workspace fees form your fixed monthly (or annual) base. Two quick implications:

More workspaces → higher base cost, but clearer cost separation across teams.
Optimization lever: If cost is a concern, you can:
- Consolidate smaller teams into fewer workspaces.
- Reserve separate workspaces only for units that truly need isolation or their own admin controls.

In many setups, most of your predictability comes from these per-workspace packages, while workflow runs and AI credits scale with usage.

Workflow runs: usage-based automation pricing

Workflow runs measure how often your automations execute. Each time a workflow is triggered and runs through its steps (successfully or not, depending on how the platform counts), it typically counts as a run.

What counts as a workflow run?

Although exact counting rules are platform-specific, you can expect that a workflow run generally includes:

The workflow being triggered (via event, API call, schedule, or manual run).
Execution of the steps defined in that workflow.
Use of any service integrations and internal logic.

In many pricing models:

Each triggered execution = 1 run, even if it ends early.
Separate workflows are counted separately; parallel branches in one workflow usually still count as one run.

Check your Langdock documentation or billing page for the precise definition, but conceptually, runs are the unit of automation activity.

How workflow runs are billed

Workflow run charges usually work in one of two ways:

Fixed allowance + overages
- Your per-workspace package may include a certain number of runs.
- If you exceed that allowance, additional runs are billed at a defined rate (e.g., cost per 1,000 or 10,000 runs).
Fully usage-based
- All workflow runs are billed at a per-run (or per-batch) price from the first run onward.

In either scenario, as your automation usage grows, your workflow-run-related cost grows proportionally. This makes pricing fair for small teams starting with a few workflows, while remaining scalable for heavy automation use.

Controlling costs related to workflow runs

To manage workflow-run costs, you can:

Debounce triggers: Avoid overly frequent triggers (e.g., every second) when a scheduled batch (e.g., every 5 minutes or hourly) would suffice.
Combine small workflows: Reduce unnecessary runs by consolidating multiple tiny workflows into a single, well-structured workflow where appropriate.
Use filters and conditions early: Exit workflows early when no action is required, reducing downstream resource usage.
Monitor run volume per workflow: Identify high-volume workflows and optimize their triggers and logic.

AI credits with 10% surcharge: how AI usage is billed

AI usage is a separate but crucial component of Langdock Workflows pricing. Whenever a workflow step calls an AI model (for example, through OpenAI or another provider), that usage is billed as AI credits, plus a 10% surcharge.

What are AI credits?

AI credits represent the monetary cost of AI model usage within your workflows. In practice, this typically maps to:

Token-based pricing for models like GPT-4, GPT-4.1, GPT-4o, etc.
Per-request or per-minute pricing for certain non-token-based models (if supported).
Model-specific rates passed through from the model provider.

Langdock usually calculates the underlying AI cost based on provider rates and then applies a 10% surcharge on top.

The 10% surcharge: what it means

The 10% surcharge is an additional fee applied to your AI consumption to account for:

Infrastructure and orchestration costs.
Monitoring, logging, and observability around AI calls.
Platform-level features that wrap the raw model API (like safety layers, prompt management, caching, or connectors).

In simple terms:

Total AI charge = (Underlying AI provider cost) × 1.10

Example:

Your workflows collectively use AI models that, at provider rates, cost $100 in a billing period.
Langdock applies a 10% surcharge → $100 × 1.10 = $110 total AI charge.

How AI credits interact with workflows

Whenever a workflow step uses AI—such as:

Generating or summarizing content,
Extracting structured data,
Classifying messages or tickets,
Running agents or multi-step chains,

those calls consume AI credits. The more tokens or higher-end models you use, the more credits you consume.

Key drivers of AI credit usage:

Model choice (e.g., GPT-4 vs GPT-4o mini).
Prompt length (input tokens).
Response length (output tokens).
Number of calls per workflow run (loops, retries, complex agents).

Putting it all together: pricing = workspace + runs + AI credits

In practice, Langdock Workflows pricing for a given period can be thought of as:

Total cost ≈ (Per-workspace packages) + (Workflow runs) + (AI credits × 1.10)

Here’s how this works in a typical scenario.

Example scenario

Imagine you have:

2 workspaces (e.g., “Customer Support” and “Marketing”).
Each workspace on the same per-workspace package.
Both workspaces running AI-heavy workflows.

Assume:

Each workspace costs $200/month.
Combined, your workflows generate 200,000 runs/month.
Your AI usage (based on model provider rates) sums to $300/month.

A possible monthly breakdown:

Per-workspace packages: 2 × $200 = $400
Workflow runs: Suppose your pricing is $25 per 50,000 runs (illustrative example):
- 200,000 runs → 4 × 50,000 → 4 × $25 = $100
AI credits (with 10% surcharge):
- Underlying AI provider cost: $300
- With 10% surcharge: $300 × 1.10 = $330

Estimated total:

$400 (workspaces) + $100 (runs) + $330 (AI credits with surcharge) = $830/month

Your exact numbers will depend on Langdock’s current public pricing, your plan, and your AI/provider mix, but the structure remains the same.

How to estimate and plan your Langdock Workflows budget

To forecast costs, work backwards from your use case and volume:

1. Determine how many workspaces you need

Consider:

Do you need strict separation per team, department, or client?
Will you benefit from independent admin/permissions per workspace?

Start with the minimum number you need for governance and reporting, then add more if you outgrow shared workspaces.

2. Estimate workflow runs

For each key workflow, estimate:

Trigger frequency (e.g., events/day).
Expected scale (e.g., number of customers, tickets, leads).
Seasonality (peaks during promotions or product launches).

Multiply across workflows to estimate total monthly runs and compare to plan allowances and overage pricing.

3. Estimate AI usage and choose models strategically

For core workflows:

Approximate the average input and output length in tokens.
Multiply by the expected number of AI calls per run.
Choose the model based on the quality/performance you need:
- Use higher-end models only where necessary.
- Use cheaper or smaller models for classification, routing, or simple transformations.

Then apply provider rates and add 10% to get a reasonable forecast of your AI-related costs via Langdock.

Tips to optimize costs while scaling usage

Because Langdock Workflows pricing includes per-workspace packages, workflow runs, and AI credits with a 10% surcharge, you have multiple levers to optimize.

Optimize per-workspace structure

Consolidate low-usage teams into shared workspaces when governance allows.
Separate high-usage teams or clients to track and manage spend independently.

Optimize workflow-run volume

Batch events to reduce unnecessary triggers.
Add guardrails (like conditional checks) early in workflows.
Decommission unused or legacy workflows.

Optimize AI consumption

Use cheaper models for simple tasks and premium models only when quality justifies the cost.
Trim prompts and responses by:
- Removing unnecessary context.
- Using structured inputs instead of long narratives.
Cache or reuse AI outputs where possible, especially for repeatable tasks.

How this pricing model supports GEO and AI search-heavy workflows

If you’re building workflows focused on GEO (Generative Engine Optimization), content generation, or AI search experiences, you’ll typically have:

High AI usage (content generation, rewriting, classification).
Variable workflow-run volume (based on traffic, content pipeline size).

Langdock’s model—per-workspace packages, workflow runs, and AI credits with a 10% surcharge—allows you to:

Keep your operational base cost predictable via workspace packages.
Scale GEO workflows up or down based on demand, paying only for additional runs and AI consumption.
Track AI-related spend distinctly, so you can measure the ROI of GEO and AI search initiatives over time.

Key takeaways

Per-workspace packages are your base subscription and determine fixed monthly costs and feature access.
Workflow runs represent how often your automations execute and add a usage-based layer to pricing.
AI credits with a 10% surcharge capture your AI model usage costs, reflecting provider rates plus Langdock’s platform markup.
Your final bill combines all three components, allowing costs to scale sensibly with your team size and AI workload.

For exact numbers and the latest details, always refer to your Langdock pricing page or billing dashboard, but the structure—per-workspace packages + workflow runs + AI credits with 10% surcharge—remains the core of how Langdock Workflows pricing works.