The systems people log into every morning — internal platforms, operator tools, line-of-business databases.
Open practiceThe browser-facing layer — web apps, customer portals, and open-source developer products.
Open practiceHosting, CI/CD, observability — sized to the workload, kept running by the team that built it.
Open practiceTeam enablement, on-call coverage, and clean handover — most of what we ship, we keep operating.
Open practiceMunich studio. Most engagements start with a 30-minute call.
info@arantic.comMost of our work. The kind of software a business actually runs on — bespoke to the company, not a re-skinned template. CAPzone360, the closed-source platform we run for CAPTRON, is the canonical example: built end-to-end, then kept running.
In practice
CAPTRON · CAPzone360
Like CAPzone360, the closed-source workspace we built and run for CAPTRON: centralised product data, role-based access, SSO, file management, and audit trails for a 40-year industrial sensor manufacturer with offices across the EU, US, and China.
CSV and Excel imports with draft-review-before-commit workflows, configurable field definitions, and idempotent re-runs — so the people maintaining a 5,000-SKU catalog are not babysitting the import.
Industrial document pipelines: parsing, validating, and generating IODD, PSET, and other vendor XML formats — extraction and routing for invoices, orders, contracts, datasheets.
Glue between systems of record and the operator-facing tools that read them. The legacy box nobody documented, talking to the new one we just shipped.
Tablet and terminal interfaces designed for the line — high-contrast, gloves-on, one-thumb operable, and resilient to a flaky shop-floor network.
Operational reporting and notification systems pulled from the systems of record — not pasted from CSVs — with audit logs of who approved what, and when.
Engagement · project + retainer
Include in your first email
Continue
The browser-facing layer — web apps, customer portals, and open-source developer products.
