Technology · operations · transparency
Technology that fits the task and the responsibility
A good technical foundation stays in the background: it loads quickly, can be maintained and makes it clear where your data lives and who is responsible. This page explains the tools and operating models Formatgeber can generally use.How website and infrastructure work together
A clear technical foundation connects your website with a controllable operating model.01Your presence
Website or web app
Fast, clear and matched to your business02Delivery
Deployment
Traceable releases without unnecessary manual work03Operations
Server in Germany or the EU
A suitable environment with clear access and responsibilities04Protection
Backups & monitoring
Secure, check and react early when something goes wrongWeb design and development
Websites are not built from one fixed technology recipe. Depending on the goal, they may use custom frontends, WordPress, WooCommerce or applications with their own data and workflows.WordPress and WooCommerce
WordPress is useful when you want to manage content yourself and need an established, extensible foundation. Themes, plugins, updates, backups and permissions are selected to avoid unnecessary maintenance.Custom web applications
Internal web apps, customer portals, admin interfaces, integrations and automations can be built when standard software does not fit the workflow.Design system and components
Reusable design elements create a consistent appearance and make future extensions more predictable. Components are responsive, semantic and designed for keyboard use.Hosting and operations
Websites can run on existing infrastructure, with a suitable provider or in an exclusively operated environment. Locations, access, backups, monitoring and responsibilities are documented.German and European infrastructure
Operation can be planned in Germany or the EU. This can simplify data-flow decisions, but a location statement is not a blanket legal guarantee.Virtual, root and managed servers
More control also brings more responsibility. A managed model can cover defined operating tasks; the right option depends on access, performance, security and budget.Docker, Coolify and deployment
Containerised applications can be separated and operated reproducibly. For clients, that primarily means traceable deployments and fewer manual errors.Proxmox and virtual infrastructure
Proxmox can separate several virtual systems on suitable infrastructure. It is useful when services need independent operation and backups, not a default recommendation for every project.Open-source systems
Nextcloud, Matomo, Vaultwarden and other established systems may be suitable. Selection depends on users, data, integrations, security and operating effort.Backups and monitoring
Backups are useful only when recovery and retention are defined. Monitoring should make relevant outages visible early; scope and responsibilities are agreed in the contract.Domains, DNS and email migration
Domains and DNS connect websites, mailboxes and external services. Migrations plan addresses, redirects, authentication and the switchover. Private mail servers require a separate review.Privacy, security and maintenance
Secure access, minimal permissions, updates, backups and transparent providers form the technical basis. Ongoing support can include updates, checks, monitoring and defined response services.Technical boundaries
Not every wish fits every budget, service or privacy requirement. Server, domain, licence and provider costs may be additional. Legal and binding privacy advice is not included by default.Frequently asked questions
Do you work only with open source?
No. Open source is one option. The right fit depends on the task, budget, data and long-term operation.
Can I take over the infrastructure later?
Yes, if handover, access, documentation and responsibilities are agreed accordingly.
What does a managed server mean?
It is not a uniform legal term. The offer specifies which updates, backups, monitoring and response services are included.