One REST call in, one signed webhook back
You ship an app with user content and need Art. 16, 17 and 20 DSA plus the store rules, but not a moderation back office of your own. Limenia plugs into your backend, and your team decides in the dashboard.
What Limenia brings to it
REST API and signed webhooks
Reports, appeals and reviews via POST from your backend. Decisions come back as webhooks signed with HMAC-SHA256, with retries and a delivery log.
Examples for seven backends
Node.js, Python, Go, PHP, AWS Lambda, Supabase Edge Functions and Firebase Cloud Functions, public on GitHub under Apache 2.0.
A guide written for coding agents
The integration guide, the OpenAPI file and llms.txt are written so your coding agent can build the integration itself.
Firebase and Supabase connectors
Bans take effect directly in Firebase Authentication or Supabase Auth, even if your webhook receiver happens to be down (Pro).
Store checklist
Apple’s and Google Play’s rules for each app: what Limenia can detect is ticked for you, you tick off the rest.
Plans by number of apps
Basic for 1 app, Pro for up to 5, Premium for up to 20. No plan limits the number of reports.
What you would otherwise build yourself
A report button is quick to build. The DSA and the stores ask for more: handle notices in a traceable way (Art. 16), explain every restriction with all the required details (Art. 17), tell reporters the outcome, and, depending on your size, run an appeals process for at least six months (Art. 20) and publish a transparency report. On top of that you need a dashboard where your team decides, with roles, an audit log and retention periods.
The guide The DSA for apps explains which duties apply to your app. Build or buy content moderation? compares the options and what to look for.
How Limenia plugs into your backend
App ──▶ your backend ──▶ Limenia POST /v1/reports
App ◀── your backend ◀── Limenia Webhook decision.created
- Your app calls your backend. The backend takes the reporter from the login, loads the content from your own database and sends the report to Limenia.
- Your team decides in the dashboard. Limenia writes the statement of reasons under Art. 17.
- Limenia sends the decision back as a signed webhook. Your backend verifies the signature and applies the action. With the Firebase or Supabase connector, a ban also takes effect directly at sign-in.
Firebase and Supabase have their own guides: Report and ban users in a Flutter app with Firebase and How to ban a user in Supabase. The integrations page shows every path.
Written for coding agents
The integration guide is public. It starts with hard rules for agents, walks through the paths for Firebase, Supabase, Node.js, Go, Python, PHP and AWS Lambda step by step, and ends with a go-live checklist. There is also the OpenAPI file and llms.txt. The runnable examples are in the examples repository on GitHub.
Ready for store review
Apple’s Guideline 1.2 asks apps with user-generated content for a filter, a way to report content with timely responses, the ability to block abusive users, and published contact information. Google Play asks for similar things. The store checklist in Limenia shows for each app what is done and what is missing. The guide App Store Guideline 1.2 goes into detail.
For agencies
If you build apps for several clients, each client gets its own tenant. Apps, reports, retention periods and billing stay cleanly separated, and every client can have its own plan. You sign in once and switch between your clients in the dashboard. In each tenant you have your own role, for example admin, and your client can invite their own moderators. We set up new tenants for you on request.
Pricing
Plans follow the number of apps you run: Basic €39 per month for 1 app, Pro €149 for up to 5 apps, Premium from €499 for up to 20 apps. All prices exclude VAT. Every mandatory feature is in every plan. New accounts try every Pro feature for 30 days, only without the AI pre-check. See all plans.
This page explains the law in general terms and is not legal advice. Have your own case checked. Firebase, Supabase, Flutter, Apple and Google Play are trademarks of their respective owners.
Ready in three steps
One case in the dashboard, from the report to the result in your app.
Report
Your app sends reports with a simple API call. Reports about the same content are bundled into one case.
Decide
Your team reviews in the dashboard and decides with reasons under the DSA. With the AI pre-check, a suggestion is already waiting.
Enforce
Limenia sends the decision and its reasons back to your app, which puts it into effect. Every delivery is in the log.
For developers
One REST call in, one signed webhook back. Examples for seven backends are on GitHub.
POST /v1/reports
Authorization: Bearer lm_live_…
{
"source": "user",
"reasonCategory": "spam",
"subject": {
"externalUserId": "u_112"
},
"content": {
"externalContentId": "c_5521",
"contentType": "comment"
}
}Frequently asked questions
Your question is not here? Write to us, a person will answer.
Go to the contact formCan my app call Limenia directly?
No. The API key belongs in your backend, never in the mobile or web app. The app calls your backend, which takes the reporter from the login and forwards the report to Limenia. A Cloud Function or Edge Function is enough.
Do I need a connector?
No. The signed webhook covers every decision. A connector is worth it if bans should take effect directly in Firebase Authentication, Supabase Auth or RevenueCat. Connectors come with Pro.
Are there packages for Flutter?
Yes. The limenia package is public on pub.dev (pub.dev/packages/limenia), with ready-made widgets for the report sheet, complaint form, statement of reasons and a notice for restricted accounts. For the device connector there is the optional limenia_device. The integration still runs through your own backend, and the API key stays there.
Can my coding agent build the integration?
Yes, that is what the public integration guide is written for. It has hard rules (for example: the API key stays in the backend), paths for common backends, the API reference and a go-live checklist. Give your agent the link to the guide or to llms.txt.
Can an agency manage several clients?
Yes. Each client gets its own tenant with its own apps, data, retention periods and plan. You sign in once and switch between tenants. In each client team you have your own role, and the client can work in it too. We set up new tenants on request.
What does Limenia cost?
Basic is €39 per month for one app, Pro €149 for up to 5 apps, Premium from €499 for up to 20 apps, all excluding VAT. New accounts try every Pro feature for 30 days, only without the AI pre-check.
Ready to connect your app?
One REST call in, one signed webhook back. The guide for your backend is on the integrations page.