Development Infrastructure
2 min

Every project needs infrastructure beyond the code itself. A code repository, hosting, continuous integration, and domain registration. How that infrastructure is owned and managed is something we discuss at the start of every engagement.

wdms offers two models.

Managed

Everything lives under wdms infrastructure. Repositories, hosting, CI, and deployments are handled entirely by wdms. The client doesn’t need to create or manage any accounts.

This is simpler. There is nothing to set up on your end. The tradeoff is dependency: your project lives on wdms infrastructure, and moving away requires a migration. Managed infrastructure carries a monthly infrastructure fee.

One exception: For mobile apps which are deployed on EU app stores you need your own Apple and Google developer accounts. See our EU Cyber Resilience Act article for why this is.

This option works well for clients who want a fully hands-off experience and prefer a single invoice covering both development and infrastructure.

Self-managed

The client owns everything. Repository, hosting, CI pipeline, domain, and any related accounts are created under the client’s own organisation. wdms is added as a developer or administrator to do the work.

  • Full portability — if you switch developers, everything is already yours. No migration, no handover negotiations.
  • Your own CI minutes, your own billing, your own access controls.
  • Complete visibility into deployments, build logs, and infrastructure costs.

What you need to set up:

  • A GitLab or GitHub organisation account.
  • A hosting account (Netlify, your own server, or another provider).
  • Domain registration under your own name or organisation.
  • For mobile apps: your own Apple and Google developer accounts (see our EU Cyber Resilience Act article for why this matters).

This is test-link HERE WE ARE

wdms can walk you through the setup or do it for you and hand you the keys.

Which one should you pick?

If you have technical staff or expect to work with multiple developers over time, self-managed is the better long-term choice. You maintain full control and avoid any single point of dependency.

If you want everything handled for you and don’t plan to manage infrastructure yourself, managed keeps things simple.

Both models deliver the same quality of work. The difference is who holds the keys.