Built for the plants that refuse to compromise.
Apex is a manufacturing execution system engineered for automotive and electronics operations at Tier-1 scale. Strict interlocks. Full genealogy. SAP-ready. Your network, your rules, your data - never ours.
Your plant, in its own voice.
Every operation reported. Every unit accounted for. Apex composes the numbers your operators, your quality team, and your directors actually trust - not yesterday's spreadsheet.
Four things Apex gets right by design.
Everything else is a consequence of these four decisions. No feature sprawl, no optional correctness, no "we'll add that in the next release."
Genealogy by default
Every unit carries its full lineage. Every Area, every Line, every Operation it touched. The machines, the operators, the parameters, the timestamps. Queryable in under 200 ms. Audit-ready at 2 a.m.
Interlock, not advice
Stations ask Apex before every operation. If a unit tries to skip a step, the station hears stop - go to the correct op first. The plant enforces its own rules.
Any station, any protocol
REST, gRPC, OPC UA, MQTT Sparkplug B - plus pull connectors for legacy SQL, file-drops, OPC DA. One canonical event schema at the center.
Retention you configure
Per-customer, per-data-class retention. Partition-drop clean delete. Legal-hold override. Tune it to the regulatory regime you answer to.
Your line.
Mapped exactly as it runs.
Pick a Variant. Assemble its route from the operations your plant actually runs. One operation can lead to many. Many can merge into one. Apex enforces the route you define - no deviations without authorization, no skipped steps, no reconstructed history.
Read the plant floor like you read a log.
One canonical event schema. ValidateFlow + ReportOperation across every station, every protocol. Query it, stream it, audit it.
Retention is configurable per event class. Hot retention runs on your appliance; warm and cold tiers can be on-prem or in your own object store. Apex never sends events out of your network. Set in retention.yaml.
The serial number knows.
Every unit carries the route it followed. The exact Area, Line, and Operation sequence. Who touched it. What the machines said. Every child serial grafted in along the way. Freeze this record for as long as the contract requires. Walk it backward into any unit, or forward from a suspect lot to every unit it reached - recall scope in a click.
A Area · L Line · OP Operation · SN Serial NumberWhen the auditor asks who, when, and why - the record already answers.
Regulated plants are won and lost on the audit. Apex signs critical actions with electronic signatures designed for 21 CFR Part 11, enforces second-person review where the standard requires it, and keeps an append-only event trail you replay - never reconstruct.
Your MES and your ERP, telling the same story.
The floor produces a unit; your ERP hears about it the right way - the right movement type, the right work center, exactly once. Not a nightly file you reconcile by hand.
Goods movements & confirmations
Per-area goods-issues, operation confirmations, and finished-good receipts - shaped per plant: movement types, storage location, work center, batch or serial. End-of-line triggers the receipt; the backflush is consumed from the record, not guessed.
SAP S/4 over OData, or open standards
Built for SAP S/4 OData with the standard CSRF handshake. For any other system, EPCIS 2.0 and B2MML (ISA-95) land alongside the posting. One adapter seam - swap the transport without touching the floor.
A durable outbox you can replay
Every message is idempotent and persisted. Goods-issue before goods-receipt ordering, retry with backoff, dead-letter, and one-click replay from the ERP Sync cockpit. Inbound order changes - quantity, reschedule, cancel - apply back, idempotently.
Packaging station
Fill the shipping box, prove every unit is the right model and passed end-of-line, preview and print the box label, post the box backflush. A licensed station that closes the loop from the last operation to the dock.
Priced to what your plant actually runs.
Not to a catalog.
Apex is sized to your footprint - the lines that move, the stations that report, the standards your auditors hold you to. A briefing with an architect produces a concrete proposal, not a quote from a spreadsheet.
Core site license
One on-prem deployment inside your network. Sized to the number of production lines and reporting stations the plant actually runs.
Business modules
Add the outcomes you need - Floor Connectivity, Operations Intelligence, Quality Operations, Strategic Analytics, Audit-Ready Evidence. Activate the modules that fit, leave the rest dark.
Vertical solutions
Industry-tailored packs - Automotive, Electronics & EMS, Medical Device, Aerospace. Retention presets, vocabulary, audit posture already set for your standard.
Integration services
Engineer-led work to connect existing stations, legacy systems, and line-side test benches. Scoped per project, not sold by the seat.
No per-seat fees. No active-unit meter. No surprise overages. A deployment is scoped once, priced once, and renewed on fixed terms.
Talk to an architect →Stop running your plant on hope.
A 45-minute briefing with the architect behind Apex - walking through the architecture, the integration approach for your existing stations, and the deployment model inside your network. No sales gauntlet.
Common questions before the briefing.
What is Apex MES?
A manufacturing execution system that runs entirely on-premise inside your plant network. It enforces strict route interlocks, captures full unit genealogy, and exposes a canonical event stream (ValidateFlow + ReportOperation) across every station and protocol on the floor.
Is it really on-premise? No cloud at all?
Yes. The runtime, the database, and the event store all live on appliances you own, inside your network. Apex makes zero outbound calls by default - no telemetry, no license check-ins, no vendor analytics. You can air-gap the deployment and Apex still runs every interlock and writes every event.
What standards does Apex operate under?
Designed against IATF 16949, IPC-A-610, ISO 9001, ISO 13485, AS9100, FDA 21 CFR Part 11, and IEC 62443. Audit-ready exports cover device history records, electronic signature trails, and route-version diffs.
Which protocols and integrations are supported?
OPC UA, MQTT Sparkplug B, REST and gRPC out of the box, plus pull connectors for legacy SQL, file-drops, and OPC DA. Everything normalises into the same canonical event schema, so your dashboards, MOM, and SAP integrations don't fork by station.
What languages does the UI support?
English and Spanish ship by default. Additional languages are available on request - the UI is fully customisable and the platform itself adapts to any plant configuration: rename Areas, Lines, Operations, change the event vocabulary, swap labels per shift. Nothing is locked.
How is it priced?
Per-site, not per-event or per-seat. The core license covers unlimited events, unlimited stations, and unlimited operators on the licensed site. Optional add-ons (vertical packs, integration services) are quoted against actual scope, never against a catalog.
Where does my data live? Who can see it?
Your network. Your hardware. Your access controls. RbDevOps cannot see your event stream, your serial numbers, your throughput numbers, or your operator IDs unless you explicitly export and share them. The contact form on this page is the only outbound path - and it lands in [email protected], not in any analytics pipeline.
How do I get a briefing?
Use the form above. Replies come from the architect directly, usually within one business day. No sales gauntlet - the first conversation is technical.
Privacy policy.
What we collect on this site
Only what you choose to send us through the briefing-request form: your name, work email, optional company, and your message. To deter automated abuse, we briefly log the IP address and browser identifier that submitted each form. Both age out together with the message itself.
What we do not collect
No analytics. No advertising trackers. No marketing cookies. No fingerprinting or behavior profiling. The site does not load third-party scripts or remote fonts.
How your message is delivered
Your submission reaches us as an email through a transactional email provider that is contractually bound to confidentiality and may not use the contents for any other purpose. We do not retain a copy in any database, CRM, or analytics warehouse.
How long we keep it
For as long as the conversation is active, plus a short archive window after it closes. Then it is deleted along with the abuse-prevention metadata attached to it.
Your rights
If you have sent us a briefing request and want it deleted, copied to you, or corrected, write to [email protected] with the subject line Privacy request. We respond within 30 days. Where applicable law gives you additional rights (such as access, correction, deletion, or portability), we honor them.
Children
This site is not directed at children. We do not knowingly collect data from minors.
Changes
If this policy changes, the “Last updated” date above will reflect that. Material changes will also be flagged in any active briefing thread.
Terms of use.
What this site is
This is a public information and briefing-request site for the Apex MES platform. It is not the platform itself. The interactive elements you see (Route Builder, live event stream, KPI cluster, genealogy chart) are illustrative and run on simulated data inside your browser.
Permitted use
You may browse, share, and reference this site freely. You may submit a briefing request. You may not scrape the site to train models or build competitive datasets, attempt to bypass abuse protections, or use the form to send spam, threats, or malicious payloads.
Intellectual property
All design, copy, illustrations, and demo code on this site are © 2026 Apex MES. The Apex MES name and constellation mark are unregistered trademarks. Please do not use them to imply endorsement, partnership, or certification you do not have in writing.
No warranty
This site is provided “as is”, without warranty of any kind. Numbers shown in the live demos are simulated for illustration only. They are not real plant data and should not, on their own, be the basis of a procurement decision. That is what the briefing exists for.
Limitation of liability
To the maximum extent permitted by applicable law, the operators of this site are not liable for indirect, incidental, special, or consequential damages arising from your use of it. This does not limit any liability that cannot be limited by applicable law.
Governing law
These terms are governed by the law applicable to your relationship with us, with mandatory provisions of your local law applying where they cannot be waived. If any part of these terms is unenforceable in your jurisdiction, the rest remains in effect.
Changes
We may update these terms. The new version takes effect when posted. Continued use of the site after a change means you accept the updated terms.
Security posture.
Your data, your network
- On-premise by default. Runtime, database, and event store live on hardware you own, inside your network. Air-gapped deployments are supported and tested.
- No outbound calls. Apex MES does not phone home. There is no telemetry, no license check-in, no vendor analytics. The platform never sees your event stream, serial numbers, throughput, operator identities, or any other operational data unless you choose to share an export.
Built to audit cleanly
- Standards aligned. Identity, role, and audit boundaries follow IEC 62443 zone and conduit guidance. The default install ships with hardened images, deny-by-default network rules, and signed binaries.
- Immutable audit trails. Every event the platform writes is signed at write time and tamper-evident thereafter. Route-version history is preserved end-to-end and exportable for FDA 21 CFR Part 11, IATF 16949, ISO 13485, and AS9100 audits.
- Encryption everywhere. Data at rest is encrypted on the appliance. Data in motion is authenticated and encrypted between Apex services and the stations they talk to.
- Operator-approved updates. Patches ship as signed bundles and apply only during a window the plant approves. There is no auto-update from the public internet.
This website
This site is a public storefront for the platform. It serves no operational role. The briefing form rejects malformed and oversized submissions, deters automation, and authenticates outbound mail. The site sets no analytics or advertising cookies and loads no third-party scripts. We deliberately keep our defenses unspoken; sharing the recipe would only help the attacker.
Responsible disclosure
If you believe you have found a vulnerability in this site, or in an Apex MES platform deployment you have authorized access to, please write to [email protected] with the subject line Security report. Include a clear description, reproduction steps, and the impact you observed. We commit to:
- Acknowledging within 3 business days.
- Triaging and confirming within 10 business days.
- Issuing a fix or mitigation timeline appropriate to severity, and crediting you publicly if you wish.
Please do not publicly disclose findings before we have had a reasonable chance to remediate.