The knowledge
that stops sitting in single heads.
An AI-powered browser extension for JDE users — context-aware, multilingual, working directly in the JDE form. Reduce support tickets. Onboard faster. Stop losing knowledge.
You're entering a Sales Order. The next required field is Item Number. Use F4 to look up items by description.
JDE knowledge shouldn't live in one person's head.
Most JDE environments have the same problem: one or two power users know how everything actually works. When they're on holiday, on leave, or moving on — the knowledge goes with them. Support tickets pile up. Onboarding stalls. New hires struggle for months.
OperoGuide turns that institutional knowledge into something users can access directly — right inside the JDE form they're working on. No tab-switching. No knowledge-base hunt. No ticket queue.
OperoGuide in action.
A short walkthrough on a real JDE form — see how OperoGuide guides the user, where it gets the answer from, and what the rollout looks like.
You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationSix features. One outcome.
Built specifically for JD Edwards EnterpriseOne. Not a generic chatbot bolted onto a browser.
Browser extension
Chrome (MV3), Edge (MV3), and Firefox (MV2). One click to install. Pushed via Group Policy or self-service.
Context-aware
Detects which JDE form is open. Knows the difference between P4210 and P4310. Suggestions match what the user is actually doing.
19 languages
Detects the user's browser locale automatically. Answers in their language — even if the JDE knowledge base is in English.
Retrieval-Augmented AI
Answers grounded in your JDE knowledge base — runbooks, training docs, custom-object specs. No hallucinated function names.
Multi-tenant by design
Token-based authentication keeps each customer's knowledge base separated. Suitable for shared-service centers and group structures.
GDPR & audit-ready
EU-hosted on IONOS Germany. Full query audit log. No JDE production data leaves your infrastructure.
From install to first answer in minutes.
No JDE customization. No infrastructure changes. The extension talks to a dedicated OperoGuide tenant.
Install extension
Users add OperoGuide from Chrome Web Store, Edge Add-ons, or Firefox Add-ons. Or push via your IT policy.
Connect tenant
One-time token connects the extension to your dedicated OperoGuide backend. Token is unique to your organisation.
Open JDE
OperoGuide appears as a sidebar in any JDE form. Context is detected automatically — no setup per form.
Ask & act
Users ask questions in their own language. OperoGuide answers from your knowledge base, scoped to the current JDE form.
Where OperoGuide shows up.
Four scenarios where JDE customers see the biggest impact within the first months.
New hires productive in days, not months.
A new employee opens JDE for the first time. Instead of shadowing a senior user for weeks, they get context-aware guidance directly in each form — in their own language.
Tickets that never get raised.
Most "how do I…" tickets come from users who can't find the right answer. OperoGuide gives the answer inside the JDE form — so the ticket never gets opened.
One JDE, 19 languages.
Your JDE setup is in English. Your warehouse team in Hungary doesn't speak English. OperoGuide bridges that gap — they ask in Hungarian, get answers in Hungarian.
The knowledge stays. Even when people leave.
Your senior JDE user moves on. Their know-how lives on in the knowledge base — accessible to everyone who needs it, right inside JDE.
Which JDE versions are supported?
OperoGuide works with JD Edwards EnterpriseOne 9.1 and 9.2 across all Tools Releases that support modern web browsers. We don't require a specific Tools Release because the extension reads the rendered HTML — no server-side dependency.
Which browsers are supported?
Chrome (Manifest V3), Microsoft Edge (Manifest V3), and Firefox (Manifest V2). Distributed via the official browser extension stores, or via Group Policy / managed deployment for enterprise IT.
Where is data hosted? What about GDPR?
OperoGuide backend runs on IONOS Germany by default. The knowledge base is stored encrypted at rest. Queries are processed in the EU. We provide a full DPA (Auftragsverarbeitungsvertrag) on request.
Three deployment models are supported: EU Cloud (SaaS) on IONOS, On-premises in your data center or private cloud, or your own cloud (Azure, AWS, GCP) where we manage OperoGuide inside your existing hyperscaler tenant.
Critically: JDE production data never leaves your infrastructure. The extension reads page context but only sends the question text and relevant context tags to the AI — never database content.
How is the knowledge base maintained?
You provide your existing JDE documentation — runbooks, training material, custom-object specifications, internal wikis. We ingest, embed, and index it. Updates can be pushed continuously or in scheduled batches.
For Care customers, we maintain the knowledge base as part of the managed service. Standalone OperoGuide customers manage it themselves via our admin interface.
How long does setup take?
From signed contract to first user productive: typically 2 to 4 weeks, depending on knowledge base size. Extension rollout is hours. Knowledge base ingestion and curation is the main effort.
Can we try it before committing?
Yes — we run structured pilots. Typically a focused use case (one JDE module, one department, one language) over 4 to 6 weeks. Get in touch to scope a pilot.
How does pricing work?
OperoGuide is sized per user-base and knowledge-base scope. Care customers (Essential and above) include OperoGuide at no additional cost. Standalone customers get a custom proposal. Talk to us for a quote.
Does it integrate with our existing ticketing system?
Yes — when a user's question can't be answered confidently, OperoGuide can hand off to your help desk with the full context (JDE form, user query, attempted answers). Integrations available for Jira, Zammad, Zendesk, ServiceNow, and email.
Ready to see OperoGuide on your JDE?
The fastest way to evaluate fit is a short demo on a representative JDE form — we'll show you how OperoGuide behaves and what the rollout would look like for your team.