Avenxor designs and ships operational software for organisations that need internal tools to be reliable, auditable, and maintainable for years — not the disposable dashboards that have to be rebuilt every leadership change. Our work covers MRP and manufacturing planning, project and procurement management, admin portals, hospital and laboratory workflow systems, central monitoring dashboards aggregating embedded device telemetry, and integration layers connecting legacy hardware to modern APIs. We build with Next.js, TypeScript, PostgreSQL, and Docker on the front, and HL7 FHIR, DICOM, and SDC / IEEE 11073 on the medical interoperability side. Architecture follows the boring patterns that age well: typed APIs, migrations under version control, observability from the first day, role-based access aligned to the operational workflow. Every platform ships with deployment scripts, runbooks for the on-call team, a documented data model, and a maintenance window measured in years — so the software stays useful long after the original engagement closes, without needing the original team in the room to keep it alive.
What kinds of operational software does Avenxor build?
MRP and manufacturing planning, project and procurement management, hospital and laboratory workflow systems, central monitoring dashboards for embedded device fleets, admin portals, and integration layers that connect legacy hardware to modern APIs.
What stack do you typically use?
Next.js with TypeScript, PostgreSQL, Docker, Resend or SMTP for transactional mail, Supabase or self-hosted auth, and a typed API layer (tRPC or generated OpenAPI). On the medical side: HL7 FHIR, DICOM, IEEE 11073 / SDC where applicable.
How do you handle medical interoperability (HL7, DICOM, SDC)?
We map device and clinical data to HL7 FHIR resources, render DICOM where imaging matters, and use IEEE 11073 / SDC for live device communication in operating rooms. Avenxor has shipped this across both embedded devices and the software that consumes them.
Will the software still be maintainable after Avenxor leaves?
Yes — that is the explicit deliverable. Every platform ships with version-controlled migrations, a documented data model, deployment scripts, runbooks for the on-call team, and a maintenance window measured in years. The next team can take over without us.
Do you support and maintain the software after launch?
Optionally, on a fixed maintenance window. Many clients run the software themselves after handover and only call us back for major features or platform upgrades; others retain us as the on-call team. Both are valid engagement models.
Can you integrate with existing systems (ERP, hospital information systems, IoT brokers)?
Yes. We routinely integrate with SAP, Odoo, hospital information systems via HL7 FHIR, PACS via DICOM, and IoT brokers (MQTT, OPC UA) for industrial telemetry. The integration layer is a first-class part of the architecture, not an afterthought.
Have a software design challenge?
Let's talk.
Most engagements start with a 30-minute call. Describe the problem — we'll tell you honestly if we're the right team.