The Pexon Dispatch
AI engineering resources, from inside real projects
Published by PEXON ROMANIA S.R.L.
Cluj-Napoca
Resources is where Pexon publishes its AI engineering material: six anonymised case studies from industrial delivery with measured numbers, and field notes written by the engineers who did the work. Use cases, reference architectures and learning material are planned and not published yet, so nothing here links to a page that does not exist.
Spotlight
Claude EU Data Residency: Bedrock, Foundry or the Direct API
Only two Claude platforms keep inference inside Europe today. What Bedrock, Microsoft Foundry and the direct API each guarantee, and what pinning a region costs.
Field note
Read the field note in full →Illustration · Thomas Cole, The Consummation of Empire, 1836
Client referenceProduct Support Assistant at a Transformer Manufacturer
Illustration · Roman mosaic, Odysseus and the sirens, Thugga
Blog · technical and industry
Claude and AnthropicClaude EU Data Residency: Bedrock, Foundry or the Direct API
Only two Claude platforms keep inference inside Europe today. What Bedrock, Microsoft Foundry and the direct API each guarantee, and what pinning a region costs.
Data foundationPermission-Aware Retrieval — Why AI Pilots Die at Access Control
Enterprise AI pilots pass the demo and fail the security review. What it takes to carry SharePoint ACLs and SAP authorisations through a retrieval pipeline.
Private AILLM Quantisation Accuracy: What Four Bits Actually Costs
What four-bit and three-bit quantisation cost in accuracy, the KV cache and power arithmetic behind the decision, and how offline retrieval stays permission-aware.The desks
Your AI is not stuck on the model. It is stuck on the data underneath it.
See what the data-layer work is
Illustration · Thomas Cole, The Consummation of Empire, 1836
References · what ran in production
Transformer manufacturer · product supportEvery technical enquiry answered from decades of documentation, in seconds
An LLM-independent assistant in the manufacturer's own Azure tenant, indexing SharePoint and Confluence behind Entra ID so permissions arrive with the document.−90%Research time per technical enquiryEUR 0Recurring licence costEUR 3–5Infrastructure per user, per month- Private AI
Self-Hosted RAG Platform for 800+ Cooperative Banks
800+ banks - Company brain
Permission-Aware Maintenance Assistant at an Engine Manufacturer
+40 % first fix - Data foundation
End-of-Line Visual Inspection at an Engine Manufacturer
up to −80 % - AI governance
Multi-Agent Standards Assistant at an Automotive Supplier
300–400 engineers - AI FinOps
Model Versioning and FinOps at a Regulated Asset Manager
3 model tracks
Illustration · Huangshan, Anhui
What is filed where
- Open
Blog
Technical and industry writing from the delivery pool, filed under the business area it belongs to.
3 published - Planned
Use cases
Business value from the department's side: what a team gets, what it costs, and what has to be true first.
In preparation - Planned
Architectures
Reference architectures and worked technical examples, drawn the way we build them inside a client tenant.
In preparation - Planned
Learning
Tutorials, hands-on setup and training material you can follow in an afternoon.
In preparation
Questions about this section
What is actually published here today?
Six case studies from industrial delivery, and the technical blog. Use cases, reference architectures and hands-on learning material are named on this page as areas in preparation. None of the three links anywhere, because none of them exists yet, and a section heading that points at a 404 is worse than an empty shelf you can see is empty.
Why is there no newsletter sign-up on this page?
Because there is no newsletter. There is no list, no sending platform and no consent flow behind one, so a form here would collect work addresses with nowhere to send them and no privacy terms to govern them. If a dispatch ever goes out, the form arrives with those terms attached and not before.
Who writes the material on this site?
The engineers who did the work. A post carries a byline only where the named person has agreed to sign it, because a byline also ships as a schema.org Person node and is therefore a claim about a real employee. Anything without a name is attributed to the organisation rather than to an author invented to fill the field.
Not a sales call. An architecture call.
Thirty minutes with the architect who would actually run the engagement.