00IT company · Engineering
Systems that
hold up under
real work.
Bät GmbH is an IT company that designs, builds and maintains software, web applications and the infrastructure beneath them — with a preference for clarity, careful engineering and systems that remain understandable years after launch.
01Focus
Four connected disciplines: software, the web, the cloud, and the integrations that let them work together.
01
Software engineering
Back-end services, tooling and application logic.
02
Web applications
Browser-based products and internal platforms.
03
Cloud & infrastructure
Environments, deployment and operations.
04
Integration & automation
Connecting systems and removing manual steps.
02Software engineering
Code written to be read, changed and trusted.
We build services, APIs and application logic with explicit structure, meaningful tests and documentation that explains the decisions behind the code — so the next engineer can continue without guesswork.
- →Service & API design
- →Refactoring legacy code
- →Automated testing
- →Technical documentation
03Web applications
Interfaces with solid foundations.
From customer-facing products to internal dashboards, we develop web applications that are fast, accessible and responsive, backed by maintainable front-end architecture and well-defined data flows.
Attention goes to the parts users feel: load times, clear states, keyboard and screen-reader support, and behaviour on small screens.
04Cloud & infrastructure
Infrastructure that is described, versioned and repeatable.
We set up and maintain cloud environments using infrastructure as code, so that environments can be reviewed, reproduced and rebuilt rather than hand-assembled.
Deployment pipelines, monitoring, logging and cost awareness are treated as part of the system, not an afterthought.
05Integration & automation
Fewer copy-paste steps. More reliable flows.
Many organisations run on several systems that do not talk to each other. We connect them through APIs, message queues and scheduled jobs, and automate repetitive processes with clear error handling and visibility.
- 01MapIdentify systems, data owners and current manual steps.
- 02DefineAgree on interfaces, data formats and failure behaviour.
- 03ConnectImplement integrations with retries, logging and alerts.
- 04AutomateReplace repetitive tasks with observable jobs.
- 05ObserveMeasure, review and refine over time.
06Security & reliability
Security is a habit, not a phase.
Least privilege
Access is scoped to what each person and service actually needs.
Secrets hygiene
Credentials are kept out of code and rotated where practical.
Dependency care
Third-party packages are tracked and updated deliberately.
Backups & recovery
Recovery procedures are documented and tested, not assumed.
07Delivery process
Short cycles, visible progress, shared decisions.
1
Discovery
Understand goals, users, constraints and existing systems.
2
Scoping
Define a first phase with clear deliverables.
3
Build
Iterate in short cycles with regular reviews.
4
Launch
Release carefully, with monitoring in place.
5
Support
Maintain, improve and hand over knowledge.
Principle 01
Simple over clever
The best solution is usually the one the next person can understand quickly.
Principle 02
Measured, not assumed
Performance and reliability decisions are based on observation.
Principle 03
Reviewed by default
Changes are peer-reviewed, tested and traceable.
08Illustrative scenarios
What an engagement could look like.
The following are hypothetical examples meant to illustrate typical problems. They are not descriptions of real clients or completed projects.
Example A
A retailer with disconnected stock data
Order and inventory systems update each other overnight via spreadsheet exports. An integration layer could synchronise them through APIs with alerts on failures.
Example B
A growing internal tool
A small internal web app has become critical but is hard to change. A staged refactor with tests could make it safe to extend.
Example C
Manual server setup
Environments are configured by hand and differ subtly. Infrastructure as code could make them reproducible and reviewable.
09Questions
Frequently asked.
- What kind of work does Bät GmbH take on?
- Software engineering, web application development, cloud and infrastructure work, and systems integration and automation. Engagements can cover a single area or combine several.
- Do you work on existing systems or only new ones?
- Both. Much valuable work happens inside existing systems: stabilising, extending, migrating or integrating them. New builds are approached with the same attention to long-term maintenance.
- How does a collaboration usually begin?
- With a conversation about the problem, the constraints and the intended outcome. From there, a scoped first phase is proposed so that both sides can evaluate the fit with limited commitment.
- Who owns the code and documentation?
- Ownership and licensing are agreed in writing for each engagement before work begins.
- How do you communicate during a project?
- Through regular, written progress updates, shared task tracking and scheduled reviews, adapted to the tools and rhythm your team already uses.
- How can I get in touch?
- Write to [email protected] with a short description of what you are working on.
