For product & tech
An integration your engineers can verify.
If you're evaluating Logora from the product/CTO side, here is what matters : how it integrates with your stack, how it scales, what it does to your core web vitals, and how it logs in production. No fluff.
Join the debate
Sign in to comment.
One reader account for Ouest-France subscriptions, comments and debates.
or use
No double login · Subscriber identity travels with you · GDPR-compliant
- 99.96% API uptime over the last quarter (status.logora.fr · 5 services monitored) Q1 2026
- 5 SDKs JS, WordPress, server-side, AMP, webview · docs.logora.fr Public docs
- ~2h your team's time on the SSO bridge, the rest handled with you Client report
Your reality today
What your day actually looks like.
-
Integration with vague timelines
Most comment vendors promise "easy integration" then need 6 weeks of back-and-forth with your tech team. The JS snippet drops, but the SSO, the paywall hooks and the auth bridges drag on.
-
Black-box production behaviour
When the comment widget breaks, you have no observability. The vendor sees their side, you see your side, and the bug investigation is a conference call.
-
Roadmap you don't influence
You ship a ticket that you need fixed, the vendor adds it to the queue, and six months later you're still waiting. The roadmap is not yours.
What changes
With Logora, here is what shows up in your reports.
-
99.96%
API uptime over the last quarter. Five independently monitored services (CDN, API, Render API, Moderation, NLP) with public status page at status.logora.fr.
-
Public API
REST API, JS SDK, WordPress plugin, AMP SDK and server-side integration. Everything documented at docs.logora.fr.
-
EU-hosted
Runs on OVH in France. Data never leaves the EU, with GDPR and DSA posture built in.
The modules that matter to you
Where to look first.
-
Documentation publique
Public API reference, JS / WordPress / AMP / webview SDKs, SSO guide, configuration. Same docs we use internally.
Explore -
Status page · 99.96% uptime
5 services monitored (CDN, API, Render, Moderation, NLP). Incidents and resolution times public.
Explore -
SSO & auth
OAuth 2.0 / OIDC / JWT with backchannel-logout, compatible with Auth0, Okta, Keycloak or a custom IdP.
Explore -
What we ship
Live changelog across LogoraDebate, LogoraAPI, LogoraAdmin, interface and LogoraModeration.
Explore
"We integrated Logora in two weeks, not six months. The OAuth bridge took two hours of our team's time. The rest, they handled with us, including the moderation policy and the locale config."
Quick answers
What we hear on every call.
-
How heavy is the snippet on page performance?
Light. The end-of-article embed is 8 KB, served from a CDN, and the API call answers in 10 ms median. The debate-space script is 60 KB and loads on user interaction. The code is pre-rendered, so it can be inserted server-side on performance-critical pages.
-
What is exposed via the public API?
Comments, moderation actions, debate state and user data, as JSON over REST, plus webhooks for events such as a new comment, a moderation decision or a user signup. Tokens are scoped per outlet and rate-limited.
-
Can we self-host?
No. Logora runs as a hosted SaaS on OVH, in France. Keeping the infrastructure in our hands is what sustains the GDPR and DSA posture and the quality of the moderation pipeline. If self-hosting is a hard requirement, the open-source option is Coral (Vox), see our comparison.
-
How do you handle reliability and incidents?
We publish live service status and uptime at status.logora.fr, with monitoring on the API and the debate services. Response times and SLAs are documented per contract.
-
Do you support our framework or CMS?
A framework-agnostic JavaScript SDK, a WordPress extension, server-side insertion, and a Google AMP SDK. Integration does not depend on your CMS.
A vendor that your engineering team can verify.
A 60-min call. We walk through the API, the SDKs, the SSO flow and the observability. We share Lighthouse traces on request. You leave knowing whether Logora fits your stack, or doesn't.