ERP and management software
Production and test instances, database, document storage, scheduled jobs, migration environments.
A business application does not always fit the mould of standard hosting. At D&D, the environment is built for the application — not the other way round.
Examples of application families, with no client references: our clients are not sales arguments.
Production and test instances, database, document storage, scheduled jobs, migration environments.
Multi-tenant applications, with the corresponding development, staging and production environments.
Internal applications, extranets, portals, custom-built management tools.
Exposed services, processing queues, background jobs, integrations between systems.
PostgreSQL, MariaDB/MySQL and other engines, on machines sized for the database workload rather than for a fleet average.
Particular versions of a language or library, system dependencies, network configuration specific to the application.
The exact sequence depends on the project, but the outline is nearly always this one.
What it runs, what it needs, what brings it down. Actual load, peaks, data volume, dependencies, availability requirements.
Number and size of machines, separation of application and database, test environments, backup strategy, replication where it is justified.
Creating and sizing the machines, operating system, preparing the environment, putting backups in place.
Takeover from your current provider or from your own infrastructure, with a planned cutover and a way back.
System, system updates, backups, restorations, infrastructure monitoring. You keep control of the application, unless agreed otherwise.
It is written down at the start, because that is what prevents unpleasant surprises on the day something breaks.
If you would like to entrust us with more — advanced systems administration, application operations — that is a separate agreement, and it is discussed beforehand, not afterwards.
Configuration to match your requirements.
Application hosting is priced from the architecture agreed: number and size of machines, additional environments, backup strategy, replication where applicable.
What it does, what it consumes, what worries you. We will tell you what we would do.