Questions about KinetiX, answered

KinetiX talks to the Epicor REST API v2, the same service interface Kinetic uses, so the server needs REST enabled. When a connection is added, epi doctor reports the Epicor version it finds and which checks pass. Sign-in uses an Epicor username and password. Kinetic Cloud sign-in through Epicor's identity provider is not supported yet.

No. KinetiX is a hosted service that calls your Epicor REST API, so nothing is added to the server. The server does have to be reachable from the internet over HTTPS. If it sits behind a firewall, publish the REST address or use a tunnel. The epi command line runs from a consultant's own machine and can reach servers the hosted service cannot.

It depends on your server, not on KinetiX. An administrator opens /admin, signs in with a code sent to their email, adds the server address, company and credentials, and presses Check. After that, people open /chat and sign in with their own Epicor account. The slow part is usually getting REST reachable and agreeing who may use it, so a Pilot plan includes guided setup.

Yes. Each Epicor environment is its own connection, and people pick one when they sign in, so you can test on Pilot first. When something is ready, ask KinetiX to promote it: BAQs, BAQ reports and menus are planned against both environments, shown to you for approval, and then copied. It never overwrites an existing item.

No. Questions are read-only lookups. A record edit, or a BAQ, report or menu build, appears as a card with the exact fields first, and nothing runs until you press the approve button. Decline leaves Epicor as it was. KinetiX proposes one change at a time. A connection that was authorized read-only refuses changes even after approval.

Your own. Each person signs in with their own Epicor username and password, and reads and approved changes run under that account. If Epicor would refuse an action for you, it refuses it in KinetiX. There is no shared super-user.

The API key and password saved for an Epicor connection are encrypted with AES-256-GCM before they are stored, and the admin page never shows them again. A person's own Epicor sign-in is held inside their sign-in grant, which the OAuth provider encrypts with a key only the token holder has.

The chat runs on Cloudflare Workers AI. Cloudflare's Workers AI data usage page states that it does not use Customer Content processed by Workers AI to train AI models, and that it does not retain inputs or outputs after a standard request is answered. KinetiX does not train models itself. Read that page for the exact terms, because they are Cloudflare's to state.

Your chat history stays in your own browser, on your device, until you sign out or delete a chat, and the open chat is sent with each request. KinetiX does not keep a server-side transcript or a copy of your Epicor data to answer from. Your question, and the Epicor results it needs, are sent to the model to write the answer.

Yes. KinetiX runs an MCP server at /mcp with OAuth 2.1, so Claude, ChatGPT and other MCP clients can connect. Each person signs in with their own Epicor account and chooses on the consent screen whether the client may also make changes. Without that grant, tools that change data are refused. The approval card is part of KinetiX's own chat. In other clients, change tools are marked as such so the client can ask you first.

Yes. Describe the result, for example open purchase order lines by vendor. KinetiX checks the tables and fields against Epicor, validates a BAQ without saving it, then shows an approval card. A full build goes in order: the BAQ, then a report on it, then a menu entry for the report, each step waiting for your approval.

Yes, the model can misread a question. That is why every answer lists the lookups behind it: the service that was called, the filter, and how long it took. You can check the source line before you rely on a figure. Counts come from Epicor's own count, not from the model adding up rows.

KinetiX reads from Epicor live, so it cannot answer questions about your data while the server does not respond. It has no copy to fall back on. epi doctor diagnoses a connection without writing anything and shows which check fails: reachability, sign-in, version or company.

No. epi audit --cloud and the epicor_cloud_readiness tool only read. They give a verdict and a list of findings: code the cloud rejects, credentials in code, classic customizations, duplicate BPMs, menus without a Kinetic screen, API keys and integrations. Every fix stays with you. When you ask KinetiX to change something, it shows the change for approval first.

It finds what Epicor itself can show: linked companies, external systems and BAQ datasources, on-prem hosts and paths in settings, EDI trading partners, data exports and API keys. Some integrations run outside Epicor and cannot be seen over the REST API, so the report lists them as a manual checklist: Service Connect workflows, reports or ETL reading the SQL database directly, programs signing in with a username and password but no API key, and file drops on network shares.

Read access to the customizations, which a user who can open the BAQ, BPM and menu designers has. Checking API keys also needs Security Manager rights. Without them, the API key checks are skipped and the report says so, rather than reporting the keys as fine.

Yes. epi pull writes your customizations to files, including the code inside BPMs and functions. If someone wrote a password or key into that code, the files contain it too. Store exports the way you store database backups, keep them out of shared folders and public repositories, and rotate any credential the readiness check reports.

Prices are in US dollars, before tax. A Pilot starts from $3,000 one-off for 60 days and up to 10 users, and is credited to your first year of Team. Team is $25 per user per month plus $500 a month for each Epicor company, billed yearly. Enterprise, for several companies or sites, is quoted from $3,000 a month. You contract with OpexCG through an order form, not a checkout.

Yes, that is what the Pilot plan is for: one connection to a Pilot environment, used by a small group, with guided setup. You see it answer questions about your own data before anyone decides on Live.

OpexCG. Guided setup is part of Pilot, onboarding is part of Team, and priority support and a security review are part of Enterprise. Write to marketing@opexcg.com or use the contact form, and say which plan you are asking about.