Documentation Index
Fetch the complete documentation index at: https://docs.linquid.io/llms.txt
Use this file to discover all available pages before exploring further.
Plans, Pricing, and Limits Reference
This page is the operator reference for what each plan unlocks and what it limits.
Plan pricing
| Plan | Monthly | Yearly |
|---|
| Starter | $0 | $0 |
| Plus | $9 | $99 |
| Pro | $29 | $299 |
| Agency | $189 | $1899 |
| Enterprise | Custom (starts at $499) | Custom (starts at $4990) |
Included plan credits
| Plan | Monthly included credits | Yearly included credits |
|---|
| Starter | $0.00 | $0.00 |
| Plus | $10.00 | $100.00 |
| Pro | $30.00 | $300.00 |
| Agency | $200.00 | $2000.00 |
| Enterprise | Custom | Custom |
Notes:
- Starter has no monthly plan-credit allocation.
- Yearly allocations are provisioned for the full year.
Credit consumption model
| Action | Cost |
|---|
| Standard click | $0.0001 |
| Conversion event | $0.0001 |
| Fraud check | $0.003 |
Top-up controls
| Setting | Value |
|---|
| Minimum top-up | $5.00 |
| Maximum top-up | $999.99 |
| Default auto-recharge threshold | $1.00 |
| Default auto-recharge amount | $10.00 |
| Auto-recharge cooldown | 60 minutes |
| Auto-recharge auto-disable after failures | 3 failures |
Resource limits by plan
| Resource | Starter | Plus | Pro | Agency | Enterprise |
|---|
| Links | 25 | 500 | 50,000 | 500,000 | Unlimited |
| Campaigns | 1 | 5 | 25 | Unlimited | Unlimited |
| Rules per link | 10 | 50 | 200 | Unlimited | Unlimited |
| QR codes | 10 | 50 | Unlimited | Unlimited | Unlimited |
| Custom domains | 0 | 1 | 3 | 10 | Unlimited |
| Team members | 1 | 2 | 5 | 25 | Unlimited |
| Workspaces | 1 | 1 | 3 | 10 | Unlimited |
| API keys | 0 | 1 | 5 | 20 | Unlimited |
| Tags | 5 | 25 | Unlimited | Unlimited | Unlimited |
| Folders | 0 | 10 | 50 | Unlimited | Unlimited |
| Webhooks | 0 | 2 | 5 | 20 | Unlimited |
| UTM templates | 3 | 10 | Unlimited | Unlimited | Unlimited |
Important:
- Numeric limits show capacity ceilings.
- Actual availability also depends on feature gates.
- If a feature family is not enabled for your plan, the corresponding module can remain unavailable even if a numeric slot exists.
Retention limits by plan
| Data family | Starter | Plus | Pro | Agency | Enterprise |
|---|
| Raw click retention | 7 days | 30 days | 90 days | 547 days | 730 days |
| Conversion retention | Not available | Not available | Not available | 547 days | 730 days |
| Aggregate retention | 30 days | 90 days | 180 days | Forever | Forever |
| Export history | Not available | 30 days | 90 days | 547 days | 730 days |
Feature-gate summary
| Feature family | Minimum plan |
|---|
| Deep links, API access, advanced routing dimensions | Plus |
| Fraud detection and fraud-scored rules | Pro |
| Revenue tracking, S2S, pixel SDK, webhooks, affiliate system, integrations | Agency |
| Custom JS, white label, SAML/SSO | Enterprise |
Plan selection workflow
- List required modules first (not only expected resource volume).
- Confirm minimum plan for every required module.
- Estimate monthly cost exposure from clicks, conversions, and fraud checks.
- Choose monthly vs yearly based on budget policy and annual commitment.
- Confirm resource ceilings for links, campaigns, users, and domains.
Use this order to avoid choosing a plan that has enough capacity but lacks required modules.
Detailed feature matrix
| Capability | Starter | Plus | Pro | Agency | Enterprise |
|---|
| Country and region routing | Yes | Yes | Yes | Yes | Yes |
| City geo controls | Yes | Yes | Yes | Yes | Yes |
| Nested rule logic | Yes | Yes | Yes | Yes | Yes |
| Device/OS/browser routing | No | Yes | Yes | Yes | Yes |
| Language and schedule routing | No | Yes | Yes | Yes | Yes |
| Query/referrer/UTM routing | No | Yes | Yes | Yes | Yes |
| API access | No | Yes | Yes | Yes | Yes |
| Deep linking | No | Yes | Yes | Yes | Yes |
| Fraud detection | No | No | Yes | Yes | Yes |
| Webhooks | No | No | No | Yes | Yes |
| Pixel SDK | No | No | No | Yes | Yes |
| Server-to-server postback | No | No | No | Yes | Yes |
| Revenue tracking surfaces | No | No | No | Yes | Yes |
| Affiliate program modules | No | No | No | Yes | Yes |
| Integrations catalog | No | No | No | Yes | Yes |
| White label controls | No | No | No | No | Yes |
| SAML/SSO | No | No | No | No | Yes |
| Custom JS controls | No | No | No | No | Yes |
Downgrade behavior (high-level)
After downgrade, these controls apply immediately:
- feature access is restricted to new tier
- unsupported features are disabled
- credits are reset to new tier allocation
- API keys may be revoked
- custom/email domain configuration may require re-setup
- extra team/member permissions are restricted
Grace behavior:
- recovery window target is 30 days for eligible items
- some settings restore on re-upgrade
- some resources require manual reconfiguration
Upgrade and downgrade validation flow
- Capture baseline feature usage before changing plans.
- Change plan and verify visible tabs/modules update immediately.
- Verify gated actions on non-settings pages as well.
- Verify billing/credits display and usage counters.
- Run one end-to-end smoke flow (link -> conversion -> analytics).
- Document any module that requires manual reconfiguration.
Operational guidance
- Treat this page as your launch contract for plan-aware operations.
- Validate plan gates in each environment before release.
- Run a downgrade simulation in non-production before billing changes.
Related:
/user-guides/manual/monetization/billing-plans-and-credits
/user-guides/manual/workspace/workspaces-and-access
/user-guides/manual/monetization/plan-gate-validation-playbook