Practices
01 Project + retainer

Custom software

The systems people log into every morning — internal platforms, operator tools, line-of-business databases.

Open practice
02 Project + retainer

Web development

The browser-facing layer — web apps, customer portals, and open-source developer products.

Open practice
03 Setup + ongoing

Cloud infrastructure

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

Open practice
04 Retainer

Training & support

Team enablement, on-call coverage, and clean handover — most of what we ship, we keep operating.

Open practice

Munich studio. Most engagements start with a 30-minute call.

info@arantic.com
Practice
03 Setup + ongoing

Cloud infrastructure

Infrastructure is plumbing. We size it to the workload, keep the failure modes legible, and make sure the people on call can read the logs at 2 a.m. The CAPzone360 stack we run — Docker, self-hosted SeaweedFS, Postgres, Redis, our own Harbor registry, EU-region pinned — is the same shape we deliver for clients.

  • EU data residency available
  • Built on standard tooling, not bespoke lock-in
  • On-call coverage available as a retainer

In practice

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

  1. 01

    Self-hosted, EU-resident deployments

    Workloads stay on EU infrastructure, on hardware you control if you want — Docker Compose stacks, self-hosted object storage (SeaweedFS), our own image registry. DSGVO-aligned, with the paper trail to prove it.

  2. 02

    Cloud migration

    On-prem to AWS / Azure / GCP, with a rollback path that we have actually tested. Or the other direction — public cloud back behind your own firewall, if compliance changed the rules.

  3. 03

    CI/CD pipelines

    Bitbucket / GitHub / GitLab, multi-environment (dev → demo → stage → prod), reproducible builds, automated tests, and deploys that are not maintained by one person.

  4. 04

    Observability

    Logs, metrics, traces wired up before they are needed — alerts you would actually wake up for, with runbooks that say what to do next.

  5. 05

    Right-sized hosting & DevOps

    From a single VPS to multi-region. We start small, instrument, and grow only when traffic earns it. No bills paying for capacity nobody uses.

  6. 06

    Air-gapped & on-prem installs

    When the data cannot leave the building — internal mirrors, on-prem orchestration, the install script that runs without ever phoning home.

Engagement · setup + ongoing

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

Continue

Training & support

Team enablement, on-call coverage, and clean handover — most of what we ship, we keep operating.