Frequently asked questions.

Custom web applications, mobile apps (native Android + cross-platform), CMS extensions and WordPress plugins, real-time platforms over WebSockets.

We also run the supporting infrastructure (Docker, Linux, Traefik) on our own racks, so the same hands that write the code keep it running. Full catalogue on the tech-stack page.

Yes, by default. We run our own racks (Forgejo, Traefik, Postgres, Linux, MapLibre tile server) and offer hosting plus ongoing maintenance as part of every engagement.

If you'd rather host on your own infrastructure, we hand over a clean deployment with documentation. No lock-in: the keys are yours either way.

Yes, regularly. The first step is a free quick look at the repository: we tell you honestly whether it's a continuation or a rewrite, and what either path realistically costs.

From there, work runs at our hourly rate by default, with time tracked transparently to the second. If you'd rather lock a single number, we can also issue a flat-rate quote with a price guarantee.

English and German.

Code, commits and documentation are written in English. Client-facing communication (calls, emails, contracts) happens in whichever of the two suits the customer best.

A free 30-minute discovery call to begin. You tell us what you want to build and ask anything; we tell you honestly whether we are a fit, and if not, we usually know who is.

If yes, we move to a line-itemised quote and a written scope. The full five-step onboarding (discovery → quote → kick-off → build & ship → maintain) is laid out on /software-development#onboarding.

Three rough tiers:

• Small: websites and configurators, usually weeks rather than months.
• Medium: large websites or pieces of custom software, multiple months.
• Heavy: custom SaaS / PaaS or live-service platforms, several months to a year, often with hosting and maintenance baked in from day one.

Once the build is live, the same person who shipped it stays on the line for ongoing changes and support.

Phone is always on for incidents, any time, any day. If we cannot pick up immediately, we call back.

For anything non-urgent, email is preferred. Long-time customers also reach us on WhatsApp. If you already run your own toolchain (Slack, Teams, a Jira board), we will join it instead of asking you to switch.

We answer during working hours and tell you proactively when we will not be reachable.

We sign your NDA, work in your project board, and stay invisible to your end-clients. Your team fronts the relationship; our hands write the code.

One explicit caveat: we will not actively lie. If a client asks point-blank whether you outsource development, we will not speak up, but we also will not deny it on your behalf. Honest non-disclosure, not misrepresentation.

When a project is finished and lives where you want it (your own infrastructure or our hosting subscription), that's the end of the obligation. We will not chase you with upsells, follow-ups or check-ins you did not ask for.

The door stays open in the other direction. New work, small change requests, a question two years later: we are reachable on pay-per-use terms whenever you need us, with no minimum commitment.

Quotes are line-itemised in plain language: no "from €X" placeholders. Once the scope is agreed, we commit to numbers we can stand behind.

Smaller engagements (a landing page, a plugin, a bug-rescue) start in the low four figures. Multi-month builds with hosting are negotiated as monthly retainers. Get an exact number by starting a conversation.

We track every minute of work to the second and bill on the first of the following month as the default cadence. Short, time-boxed projects are invoiced once on completion instead.

Invoices arrive by email in EUR with full line-items, payable by SEPA bank transfer. The hourly rate is the default; a flat-rate quote with a price guarantee is available on request, set before the work begins.

Kulanz is the Austrian word for graceful billing as a craftsman's habit, not as generosity.

If something is our fault, it does not end up on your invoice. Discounts that respect the customer are part of how we work, not a marketing line.

Code ownership. What you paid for is yours. The deliverable belongs to the customer, full stop.

Data residency. Customer data lives on our German servers (Hetzner, EU) by default, or on your own infrastructure if you'd rather host it yourself.

AI tooling. We use AI tools internally for our own productivity. On a customer codebase, AI only ever sees the code we explicitly agreed it could see, in writing.

Yes. Our public packages live on Packagist and GitHub.

Highlights: an async drop-in replacement for Laravel Reverb, a roles-and-permissions package with expiry tracking, and a WordPress plugin scaffold. We treat the catalogue as part of identity, not marketing, the longer arc is on the /about page.