Principles before products
- Prefer stable, well-supported technology with clear ownership.
- Use open standards and portable data where practical.
- Minimise unnecessary dependencies and third-party trackers.
- Design observability, backup, recovery and access controls with the system.
- Document why a technology was selected and what would trigger reconsideration.
Selection questions
Technology choices are tested against the required user journey, data sensitivity, integration boundary, expected change rate, support capability, hosting constraints and exit path. Novelty alone is not a selection criterion.
Integration and lifecycle
Before production access is requested, each connection needs a record owner, authentication method, failure path and reconciliation approach. Versioning, patching, monitoring, backup, recovery and eventual replacement are part of the decision.
Capability areas
WordPressWeb applicationsAPIsCloudData platformsAutomationAI integrationAnalytics
No partner badge or certification is implied by this list.
Last reviewed: 1 September 2026