Practice
02 Project + retainer

Web development

When 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.

  • Senior web engineers, 5+ years each
  • BugPin is live and MIT-licensed proof of work
  • Accessible, responsive, and shipped from a single team

In practice

What we actually build. Concrete deliverables we have shipped — not categories we could imagine shipping.

  1. 01

    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.

  2. 02

    Customer & partner portals

    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.

  3. 03

    SaaS dashboards & web apps

    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.

  4. 04

    Public marketing sites

    Astro and edge-deployed. Static where it can be, dynamic where it must be. This site is one we ship for ourselves.

  5. 05

    Web app modernisation

    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.

  6. 06

    Front-end for the platforms above

    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

Tell us what you're trying to ship. Most engagements start with a 30-minute call. Hourly or flat-fee, 14-day payment terms. We reply within two working days.

info@arantic.com

Include in your first email

  1. 01
    What you are trying to ship
    A paragraph is enough — we ask the rest on the call.
  2. 02
    The timeline you are working against
    Hard deadline, soft window, or open-ended.
  3. 03
    Any constraints we should know
    Data residency, on-prem, regulated industry, existing stack.
03

Continue

Cloud infrastructure

Hosting, CI/CD, observability — sized to the workload, kept running by the team that built it.