DTC's Pillars of Technology
Generalized best practices for how DTC does tech for itself and clients.
Windows Endpoints
We ensure this is always on.https://techcommunity.microsoft.com/blog/windows-itpro-blog/get-start...
Our Networks
Network Architecture
DTC's network architecture is built on firewall-centric design with complete network segmentation...
DHCP & DNS
DTC's DNS and DHCP architecture is built around one principle: the firewall is the sole DNS and D...
Remote Access
Console/Support Access Primary tool: NinjaRemote (integrated with NinjaOne RMM) Quick support fo...
VoIP Operations
Document Type: Standard Operating Procedure Audience: All Technicians (T1 / T2 / T3) & Account Ma...
VoIP Troubleshooting & Network Diagnostic SOP
Field Value **Document Type** Standard Operating Procedure — Diagnostic Field Procedure **Audienc...
Internal DNS Zone Management
Scope: All DTC-managed client environments with Active Directory Audience: T1 / T2 / T3 Technicia...
Firewall Rules & Port Requirements Master Reference
FieldDetailDocument TypeQuick Reference — InformationalAudienceAll Technicians (T1 / T2 / T3), Pr...
Our Servers (Compute)
Our Workstations
Printers & Other Peripherals
Backup & Data Protection
DTC's backup philosophy, tiered service models, RPO/RTO targets, retention standards, immutabilit...
Backup & Data Protection Standards
Backup & Data Protection Standards This document defines DTC's backup philosophy, tiered service ...
SaaS Backup Standards
This page defines DTC's standards for backing up SaaS platforms (Microsoft 365, Google Workspace,...
Cloud Backup Architecture Standards
This page defines the standard architecture for how DTC provisions cloud object storage (Backblaz...
Workload-Instance Bucket Architecture
This page defines how DTC provisions cloud object storage for backup workloads, and DTC-built app...
Device Naming Convention
DTC's standardized naming convention for all managed devices... network equipment, servers, works...
Our Identity
DTC's standards for how identity, credentials, and authentication are managed across client envir...
Our Code
How DTC writes software. Principles — not tutorials. Implementation guides (Docker conventions, b...
Build for Unreliable Integrations
Any third-party system DTC integrates with will eventually rate-limit us, drop a webhook, return ...
Writes Are Jobs, Reads Are Cached
User-facing requests never block on outbound writes. Every write to a third-party system is queue...
Everything Has a Timestamp and a Deadline
Every record in a DTC-built system answers three questions: when was I written? when did I last c...
Webhook-Driven, Reconciler-Bounded
Freshness comes from webhooks. The reconciler is what catches the webhooks that get dropped. Full...
Explicit Handling of Absent Data
NULL is not 0. NULL is not "". NULL is not false. NULL is not "no change." Treating any of those ...
Branding in the Environment, Not the Code
Company name, logos, support contacts, color palette, email footer copy, physical address — all t...
Versioned, Signed, and Tagged
Every deployment is traceable back to a specific commit by a specific author. Version numbers are...
Closed Records Are Immutable Until Proven Otherwise
A closed ticket, a paid invoice, a rejected quote — these are terminal states. They rarely change...
Observability Is a First-Class Citizen
When something breaks in production, the first question is always: "what happened?" The answer ha...
Every Integration Has a Resume Endpoint
Users close tabs. Networks drop connections. Browsers reconnect SSE streams. Servers deploy. Work...
Email Address Architecture
Email addresses are identity surfaces. Every address we publish encodes who it routes to, what tr...