How WakeTech.ai deploys
to enterprise customers.
A technical brief for Crane Worldwide Logistics IT leadership. Written for engineers and architects evaluating WakeTech.ai against shared-codebase SaaS alternatives.
One codebase, no customization, configuration only.
Modern cloud-native TMS vendors operate on a single multi-tenant codebase where every customer runs identical software against a logically-separated slice of a shared database. The vendor philosophy is one codebase, no customization, configuration only.
This model is efficient for the vendor and appropriate for customers whose operations fit inside the vendor's opinionated workflow. It fails when a customer organization cannot be represented by the vendor data model. Enterprises with hierarchical sub-divisions, federated regional offices, multiple legal entities, or industry-specific workflows that fall outside the vendor's core assumptions hit a ceiling that no amount of configuration can break through.
Four components. One coherent architecture.
WakeTech.ai operates on a hybrid architecture that preserves the engineering discipline of a single canonical platform while giving each enterprise customer the isolation, customization flexibility, and data sovereignty they need.
All WakeTech.ai customers run the same platform at the same version. Core is a single canonical codebase maintained by the WakeTech.ai engineering team. Core improvements, security patches, and new features propagate to every customer on a regular release cadence. No customer modifies core. No customer runs a forked version. This discipline is what lets us maintain high development velocity, predictable quality, and defensible security posture as we scale.
Each enterprise customer receives a dedicated deployment. Your own virtual infrastructure. Your own database. Optional landing in your own Azure tenant for strict data residency or regulatory requirements. Your own deployment lifecycle — upgrades happen on a schedule that works for your change management process. You are not forced to upgrade the day WakeTech.ai releases a new core version. You are not blocked from upgrading because another customer is on an older version.
Customer-specific behavior lives in a dedicated customization layer that sits alongside core, never inside core. Workflow extensions, custom data model extensions, custom reports and dashboards, customer-specific integrations to legacy systems, organizational model overrides for customers whose real-world structure exceeds the core platform's default assumptions, and custom UI components rendered inside core pages through defined extension slots. This is where the enterprise value lives for large customers.
The line between shared core and customer customization is enforced by engineering discipline, not convention. Core publishes a versioned extension API and commits to backward compatibility within a major version. Customization layers depend only on the published API, never on core internals. Core and customization layers deploy independently. The core test suite runs without any customer extensions loaded. Customization test suites run against a known core version and alert on incompatibility before production.
You own your data. You own your customizations. You do not own the core.
Every row, every file, every log. Stored in your database, in your deployment, under your control. Portable on request.
The extension layer code that represents your specific business processes belongs to you. If you ever leave WakeTech.ai, you take it with you.
The shared core platform is licensed to you as part of your deployment. You benefit from every core improvement we ship. You are never responsible for maintaining core yourself.
The trade: shared core gives you leverage, the customization layer gives you control, and the dedicated deployment gives you isolation. You are not a tenant in someone else's database. Your data never mixes with another customer's data. Your performance is not affected by another customer's workload. Your security posture is not coupled to another customer's security posture.
Generality decides the home, not who paid.
When an enterprise customer funds a new capability, WakeTech.ai evaluates whether it belongs in shared core or in the customer customization layer. The decision is based on generality, not who paid.
Broadly useful capabilities (hierarchical division modeling, multi-currency support, enhanced customs documentation) become part of shared core. Every WakeTech.ai customer eventually benefits. The funding customer gets the feature first, gets implementation priority, and gets recognition. Pricing reflects that the capability will be amortized across the platform.
Customer-specific capabilities (a particular legacy ERP integration, an internal GL code mapping, a proprietary carrier scoring algorithm, a compliance workflow unique to the customer) live in the customer customization layer. They are built to the customer's specification, maintained as part of the customer deployment, and do not appear in any other customer environment.
Isolation at every layer.
Each customer's data resides in a dedicated database with no cross-tenant queries possible at the infrastructure level, not just the application level.
Each deployment runs in its own network perimeter with customer-controlled ingress and egress rules.
Customer credentials, API keys, and service account tokens never touch another customer deployment.
Deployment can live in your Azure tenant. WakeTech.ai is never a data processor for customers who require data to remain under direct corporate control.
A security incident in one customer deployment cannot propagate to another. A database corruption event in one deployment cannot affect another.
Each deployment has its own audit log, its own monitoring, its own backups. You receive direct read access to your own operational telemetry.
Who maintains what.
| Component | Maintained by |
|---|---|
| Shared core platform code | WakeTech.ai |
| Core security patches and vulnerability response | WakeTech.ai |
| Core performance optimization | WakeTech.ai |
| New core features that benefit all customers | WakeTech.ai |
| Customer-specific customization layer code | WakeTech.ai delivered, customer owned |
| Customer database contents | Customer |
| Customer integrations to external systems | WakeTech.ai built, customer owned |
| Customer configuration of core settings | Customer |
| Deployment infrastructure (VMs, databases, networking) | WakeTech.ai or customer, depending on deployment model |
| Deployment upgrades and core version management | WakeTech.ai, coordinated with customer change management |