Open-source developer products
BugPin · MIT
BugPin (bugpin.io) is one we ship publicly: MIT, SQLite + Docker, a drop-in widget under 150 KB. Community and Enterprise editions, self-hosted, no SaaS lock-in.
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.comWhen the surface is a browser. BugPin — our open-source visual bug-reporting widget — is the proof: MIT-licensed, SQLite + Docker, drop-in widget under 150 KB. The same engineers ship customer portals, SaaS dashboards, and the public sites in front of the platforms above.
In practice
BugPin · MIT
BugPin (bugpin.io) is one we ship publicly: MIT, SQLite + Docker, a drop-in widget under 150 KB. Community and Enterprise editions, self-hosted, no SaaS lock-in.
React + TypeScript portals with SSO, role-based access, and EU data residency — the public-internet face of an internal platform, scoped down to what an outside user is allowed to see.
React 19, TypeScript, virtualised tables, real-time updates over server-sent events. The kind of admin UI that survives ten thousand rows without freezing the tab.
Astro and edge-deployed. Static where it can be, dynamic where it must be. This site is one we ship for ourselves.
Lifting jQuery / older Angular / aging React codebases onto a modern stack without a rewrite-from-scratch — pragmatic step-by-step migrations that keep the product usable.
The browser-facing layer when the custom-software work needs a public or partner UI — same team, no handoff, no integration tax.
Engagement · project + retainer
Include in your first email
Continue
Hosting, CI/CD, observability — sized to the workload, kept running by the team that built it.