Plans and Pricing

Last updated: 2026-10-28

Explains Lorel.ai’s pricing structure, the usage conditions and limits for each plan (Starter / Standard / Enterprise), metered usage charges, data retention policy, and what happens when you change plans.

If you subscribe through AWS Marketplace

This page describes plans and pricing for a direct contract. Through AWS Marketplace, only the Standard plan on a monthly contract is available, and pricing follows the prices shown on the product page on AWS Marketplace. The initial free credit also works differently. For details, see Subscribing Through AWS Marketplace.

Overview

Lorel.ai is an operations-automation platform you subscribe to per organization. We offer three plans — Starter, Standard, and Enterprise — to match your scale of use and operating structure.

Each plan has its own monthly base fee, usage limits, and data retention period. If your usage exceeds a plan’s free tier, metered usage charges apply according to that plan’s rules.

Note: to check your current plan, change plans, or manage your billing history and payment method, see Billing under Organization Settings.

1. Plan comparison

The base fee, usage limits, and data retention policy for each plan are below. All amounts on this page exclude tax; 10% consumption tax is added separately.

ItemStarterStandardEnterprise
Intended scaleIndividuals, small teams, evaluationMid-sized teams, the standard plan for full-scale operationsLarge-scale team operations, custom requirements
Base fee (monthly)JPY 30,000JPY 200,000Custom quote
Billing cycleMonthly onlyMonthly or annualCustom contract
Annual discountNone25% off (JPY 150,000/month equivalent, JPY 1,800,000/year total; billed monthly)Custom contract
How to sign upOnline sign-upOnline sign-upVia the contact form / individual consultation
MembersUp to 3UnlimitedUnlimited
ProjectsUp to 1UnlimitedUnlimited
SourcesUp to 10 per organizationUnlimitedUnlimited
AI agent executionsUp to 10/month (no add-on purchase)Unlimited (metered)Unlimited (metered)
Data storage free tier2GB10GBCustom
Data (telemetry) retentionFixed at 7 days30 days by default (changeable up to 365 days)30 days by default (changeable with no upper limit)
Detection event log retentionFixed at 7 days365 days (can only be shortened)Changeable with no upper limit
AI / Runbook execution log retentionFixed at 90 daysFixed at 90 daysFixed at 90 days
Initial free creditJPY 40,000 (no expiration)JPY 350,000 (no expiration)Custom

Note: In the app, Sources may appear as “data sources” (for example, “Data source limit reached for your plan. Please upgrade to add more data sources” is shown when you reach the limit).

2. Metered usage charges

If your usage exceeds the free tier included in your base fee, the following metered rates apply. Metered rates are the same on Starter and Standard (Enterprise follows the individual contract).

Billed itemMetered rateFree tierBilling unit / notes
AI agent executionJPY 200 / executionNone (*)Each execution is counted as 1. On the Starter plan, you cannot run additional executions once you reach the monthly AI execution limit of 10. Standard/Enterprise plans meter every execution you run.
Data storageJPY 200 / GBYes (Starter: 2GB, Standard: 10GB)Any amount over the free tier is billed based on your average data storage volume (GB) for the month.
Data ingestionJPY 0.01 / recordNoneEquivalent to JPY 10,000 per 1 million records. Every record ingested is billable.

(*) The “Free tier” column here is about metered billing specifically. The Starter plan’s “10 free per month” is a plan-included quota covered by the base fee (see “1. Plan comparison” above) — a separate mechanism from this metered free tier. Since the Starter plan cannot run additional metered executions once it reaches that 10/month limit, its metered free tier is “None”.

AI agent execution

  • An execution is counted the moment the agent’s analysis completes (including when it pauses in a Pending state awaiting approval, or when the follow-up after the analysis is skipped). An execution that fails with an error is not billed, but it may still count toward the Starter plan’s monthly limit of 10.
  • Test execution (dry-run) is not billed, but a separate monthly test execution limit applies on top of production executions (Starter: 5, Standard: 50, Enterprise: unlimited). Production executions are separately limited too — on the Starter plan, once you reach the monthly AI execution limit of 10 (see the table in section 2 above), no new execution can run.
  • On the Standard and Enterprise plans there is no limit on the number of executions — you are billed according to how many you run.

Data storage

  • The Starter plan includes up to 2GB free.
  • The Standard plan includes up to 10GB free.
  • Usage beyond the free tier is billed based on your average storage volume (GB) for the month.

How the data storage charge is calculated

  • The data storage charge is based on the average amount of data stored during the month.
  • Data storage volume is recorded once a day.
  • The billable amount is calculated by subtracting your plan’s free tier from the monthly average, which is the sum of your daily storage volume divided by the number of calendar days in the month (prorated by the days you were enrolled if you start or end mid-month, with days that could not be measured filled in with the previous day’s value).
  • Data storage volume is measured in bytes (1 GB = 1,073,741,824 bytes), and any fractional remainder produced when converting to GB is not rounded up.
  • The final invoiced amount is rounded to the nearest yen.
  • Even if your data volume temporarily spikes near the end of the month, billing is based on the monthly average.

Example calculation (Standard plan, 10GB free tier)

  • Days 1–15: 5GB stored
  • Days 16–31: 15GB stored
  • Monthly average storage: (5GB × 15 days + 15GB × 16 days) ÷ 31 days ≈ 10.16GB
  • Billable amount: 10.16GB − 10GB = 0.16GB

In this case, 0.16GB is subject to metered billing.

Data ingestion

  • Regardless of data size, every event or data point received by the platform is counted as 1.
  • The billing unit is 1 record.
  • Your invoice is calculated by multiplying the month’s ingested record count by JPY 0.01 per record (equivalent to JPY 10,000 per 1 million records).
  • Even if a record is later discarded because it didn’t match any detection rule condition, it is still billable at the time of ingestion.

Ingestion via webhook

  • A single webhook request is counted as 1 record.
  • Even if one request’s payload contains multiple alerts, it is still billed as 1 record.
  • If the same data is sent more than once — for example due to a network retry — every submission, including those detected as duplicates, is counted and billed separately.

Metric collection

  • Metric collection is billed on the count after deduplication.

Note on the difference between the billing dashboard’s usage figure and your actual invoice

The “metered usage” figure shown on the billing dashboard (your total usage before the free tier is deducted) is a different number from your actual invoiced amount (the excess after the free tier is deducted, plus the base fee).

3. Data retention periods

Data retention is managed independently across the following three categories.

Telemetry data

PlanRetention period
StarterFixed at 7 days
Standard30 days (changeable up to 365 days)
Enterprise30 days (changeable with no upper limit)

Detection event log

PlanRetention period
StarterFixed at 7 days
Standard365 days (can only be shortened)
EnterpriseChangeable with no upper limit

AI / Runbook execution log

Fixed at 90 days on every plan. This retention period cannot be changed.

4. What happens when you change plans

After a plan change, the new plan’s features and usage limits apply.

Upgrading

  • Your usage limits are raised to match the new plan.
  • You gain access to features available on the new plan.
  • Configuration options intended for higher-tier plans also become available.

Downgrading

Even when moving from a higher-tier plan to a lower one, your existing resources are never automatically deleted. At the time you submit the request, if any of your resource counts exceed the new plan’s limits, you cannot submit the downgrade request — first delete resources until you are within the new limit, then submit the request.

If your usage grows back over the limit between submitting the request and the effective date, what happens next depends on your billing cycle:

  • A downgrade from a monthly contract is automatically canceled if the overage isn’t resolved by the effective date (the 1st of the next month).
  • A downgrade from an annual contract takes effect on the effective date even if you’re still over the limit. In that case, your existing resources are kept, and only the creation of new resources is restricted until you’re back under the limit.
  • This applies to member count, project count, and Sources. The member count includes pending (unanswered) invitations.
  • For 30 days after a downgrade takes effect, your previous plan’s data retention settings remain in effect (and storage during this period is still metered). Any custom retention period you’ve configured on individual rules is not affected by this grace period — those settings are kept as-is. Once the 30-day grace period ends, the new plan’s retention period applies and data beyond it is deleted.

Existing resources are kept

After downgrading, the following already-created resources are kept:

  • Projects
  • Members
  • Sources
  • Other configuration

Restriction on creating new resources

For any item where you exceed the new plan’s limit, only new creation/addition is restricted.

When the restriction is lifted

Once your usage drops back within the limit — for example by deleting unneeded resources — the restriction is lifted automatically.

Conditions after downgrading

After downgrading, the new plan’s usage limits, free tier, and retention settings apply. Usage beyond the free tier is metered according to the new plan’s rates.

5. Initial free credit

A one-time free credit is granted per contract when you sign up.

PlanCredit
StarterJPY 40,000
StandardJPY 350,000
EnterpriseCustom

Terms of use

  • It never expires.
  • The free credit is automatically applied toward your invoice.
  • Both the monthly base fee and metered usage charges can be covered by it.
  • If your invoice exceeds your remaining free credit balance, the excess is billed.

6. Signing up and changing plans

New sign-up

You choose your plan and payment method (credit card or bank transfer) during the organization-creation flow after creating your account.

Changing plans

In Organization Settings > Billing, choose “Open billing management,” then choose “Change plan” in the Subscription status area to request the following changes (only an Owner can request or withdraw a plan change; the Billing role can only view contract status):

From → ToWhen it takes effect
Starter (monthly) → Standard (monthly / annual)Immediately, at the time of the request
Standard (monthly) → Starter (monthly)1st of the next month
Standard (monthly) → Standard (annual)1st of the next month
Standard (annual) → Starter (monthly) / Standard (monthly)1st of the month following the final month of the 12-month term
  • You must agree to the Terms of Service again when you request a change. Until when you can withdraw the request depends on the billing cycle you’re changing from. A change from a Standard monthly contract can be withdrawn any time before its effective date. A change from Starter takes effect as soon as you submit it, so it cannot be withdrawn. A change from an annual contract can only be withdrawn up until the request deadline below — once that deadline passes, it can no longer be withdrawn.
  • The request deadline is the same as the deadline for canceling renewal (monthly contract: the day before the last business day of your final month of use; annual contract: the last day of the month before your final month of use).
  • You cannot request a plan change while renewal cancellation is in progress, and you cannot cancel renewal while a plan change request is in progress. You also cannot request an upgrade while an invoice is past its due date (apply again after payment is confirmed), and you cannot submit a request until your organization has agreed to the latest Terms of Service.
  • For an immediately-effective change, the new plan’s full monthly base fee is charged (no proration), and no additional initial free credit is granted to make up the difference.
  • Moving to an annual contract starts a new 12-month contract from the effective date.

Enterprise plan

  • The Enterprise plan doesn’t support online sign-up.
  • It’s a custom contract arranged through the contact form.

Charges when canceling

  • The monthly base fee is never prorated.
  • Your contracted plan’s full monthly base fee applies in the month you cancel.
  • To stop being billed from the following month, cancel renewal by the cancellation deadline (monthly contract: the day before the last business day of your final month of use; annual contract: the last day of the month before your final month of use; dates are in UTC). If you miss the deadline, your contract continues until the end of the next term.

For your billing history, changing your payment method, or issuing invoices, see Billing under Organization Settings.

7. Limitations

Please note the following operational constraints.

AI agent executions on the Starter plan

  • The Starter plan allows up to 10 AI agent executions per month.
  • Once you reach the monthly AI execution limit, no new execution can run.
  • There is no way to pay for additional executions beyond the limit.
  • To run more, you need to move to the Standard or Enterprise plan.

Duplicate data via webhook ingestion

  • If the same event reaches the same Source more than once within 72 hours — for example because of a network retry — the second and later copies are treated as duplicates and excluded from rule evaluation. This helps prevent incidents from being created, or AI analysis from running, more than once for the same event. This deduplication applies only to rule evaluation: duplicates are not removed from the ingestion count, so each event treated as a duplicate is still counted as a separate ingestion and is billable.