Free where it should be. Clear where it counts.

Nothing, ever. The eBRC exporter app is free at any volume, with no certificate limit and no paid tier for exporters, and sign-up collects no card. You connect DGFT, file, and download certificates without a bill arriving.

It is free for general use: up to 250 production certificates a month and up to 10 exporter entities per account in either environment, with sandbox filing not metered. The published per-endpoint rate limits in the docs apply to everyone and protect the service.

This applies to the eBRC API only; the eBRC exporter app has no allowance to exceed. Crossing an allowance stops the work that draws on it: a live filing past the monthly certificate cap is refused with a 402 that names the figure and what you have used, and so are extractions and onboarding past their ceilings. Test filing is the exception and is never refused. Plans and your usage for the month sit together in your console, under Billing.

In your console, under Billing, once your account is set up. Plans, what each one includes, and your usage for the month sit on the same screen, so you are comparing a price against your own volume rather than against a table. A plan's volumes are totals rather than increments: the figure it includes is the monthly cap, and every plan's totals sit well above the free allowance.

Because the number that matters is what your volume costs, and that is only meaningful next to your usage. Everything that decides whether you ever pay is published here in full: the free allowance, exactly. The plans themselves are one screen away, before you are ever asked to choose. For a committed annual arrangement or anything the plans do not cover, the contact form gets you a quote.

No. An exporter filing certificates against their own IEC uses the eBRC exporter app, which is free at any volume with no certificate limit. The eBRC API is a separate product for platforms and enterprises that generate certificates from inside their own systems, across many exporter entities. If you file for yourself, the app is the whole product, and nothing about the API's allowance applies to you.

The two are separate products with separate accounts: the eBRC exporter app for filing your own certificates, and the API console with its own keys and its own published limits. Both can be used, so an exporter who later builds an integration opens a console account alongside the app rather than instead of it. Nothing needs to move: certificates already issued stay in the eBRC exporter app, whose full ledger exports to Excel whenever you want.