Development
Websites, apps, automation, smart building - built in-house, maintained in-house
When off-the-shelf software is not enough, we build. Structured, tested, documented. Our stack is deliberately modern (Rust, TypeScript, Astro, React) so your software is still maintainable in five years.
Was wir in der Säule Development machen.
3 Topics, jedes einzeln buchbar oder als Gesamt-Setup. Klick auf eine Zeile öffnet die Detail-Page.
| No | Topic | Type |
|---|---|---|
| 01 | Automation· n8n, Python, Rust - less manual work, more time for what matters | Topic |
| 02 | Smart building· Home Assistant, KNX, MQTT - building services that work together | Topic |
| 03 | Websites & web apps· Astro, React, Markdown in Git - fast, maintainable, strong on SEO | Topic |
So bauen wir.
Vier Punkte, die in jedem Projekt der Säule Development unverhandelbar sind.
About this pillar.
What we build
We build for clients who need a piece of software that does not exist off the shelf. This is not an app shop, it is craft: exactly what you need, without the bloat around it.
Websites and web apps
Our standard stack: Astro for marketing sites and content portals, React for interactive dashboards, Rust (Axum) or Python (FastAPI) for backends, PostgreSQL for data, Tailwind for styling, Biome for code quality and Markdown in a Git repository as the content source.
Why this stack:
- Everything is open source, so you depend on no single vendor
- Markdown in Git gives you version history, branch reviews and traceable changes without an extra database
- Rust backends last for years without chasing security patches through a churning dependency tree
- Astro ships static pages - sub-second load times, no hydration cost, no JavaScript bloat
Automation
n8n is our automation platform of choice. Open source, self-hosted, with more than 500 integrations. Typical use cases:
- CRM synchronisation between systems
- Extracting receipts from email into DATEV
- Ticket routing with LLM triage
- Auto-reply and lead qualification
- Collaboration access to Microsoft Graph and Google APIs
- Deployment hooks for container updates
We also write our own JavaScript or Python where n8n nodes are not enough.
Smart building
Commercial buildings are like homes with more trades involved. We integrate KNX, Modbus, Zigbee, MQTT and modern IoT protocols through Home Assistant. The result is a single dashboard for lighting, heating, shading, access, presence, ventilation and energy monitoring.
Typical projects:
- Office buildings with presence-based lighting and HVAC control
- Small production sites with energy monitoring and alerts on consumption anomalies
- Practices and law firms with access logs and an automatic end-of-day shutdown
- Holiday properties with landlord-friendly scenes
Integrations
When two systems need to talk to each other, we build the bridge. Examples:
- HubSpot ↔ Microsoft 365, bidirectional
- Practice management software ↔ DATEV
- Website ↔ CRM ↔ mail
- IoT sensors ↔ Home Assistant ↔ Grafana ↔ email alerts
How we work
- Git-first: everything in Git, including docs, deployment config and secret management
- Tested: Rust tests, Vitest frontend tests, integration tests via Playwright
- Documented: README, ARCHITECTURE.md and DEPLOY.md are part of the deliverable
- Fairly priced: fixed price for scoped features, hourly for open-ended development
- Handover-ready: you can take the code and continue elsewhere at any time
How we work together.
From the first hello to running operations in five steps.
Development - frequently asked.
FAQ.01Which programming languages do you use?
Primarily Rust and Python for backend services. TypeScript with React and Astro for frontend. JavaScript in n8n for automation. We keep the language stack deliberately narrow so we can hand projects over and maintain them without switching between ten ecosystems.
FAQ.02Why Rust and not Go or Node?
Rust gives us memory and thread safety without a garbage collector, which matters for network and IoT services. Go would be a valid alternative - but we are deeper at home in Rust and get better results in less time. We use Node for web tooling, not for production backend code.
FAQ.03Do you build WordPress sites?
No. Where clients want it, we migrate existing WordPress sites to Astro with Markdown in a Git repository - better performance, better SEO, and no dependence on a zoo of plugins. If you specifically want to stay on WordPress, we refer you to partner agencies who do it well.
FAQ.04What is the difference between your web apps and a "real" software company?
We are a real software company - but one that also knows operations and infrastructure, because we do them daily. We are not built for enterprise software with fifty developers. For specific tools, portals, automation platforms and mid-sized web apps with one to three developers, we are exactly right.
FAQ.05Smart building - is that not really building services engineering?
It is both. We work with electricians and building engineers, but we do the software layer ourselves (Home Assistant, MQTT broker, energy monitoring, presence logic, email alerts). Typically an electrician partner installs the relays and we build the logic on top.
FAQ.06Who owns the code you write for us?
You do. Always. We deliver source code, build instructions, deployment configuration and documentation - in a Git repository you have access to. Even if you keep operations with us, you can switch or fork at any time.
Sprechen wir 30 Minuten über Development.
The intro call is free. No sales pressure. We listen, check whether we fit - and tell you straight.