Tygart Media

Tag: AWS

  • I Built My Business on Google Cloud. Here’s What Happens If I Rebuild It Entirely on Amazon.

    The Thought Experiment

    Last week I published a piece on Amazon’s vertical sovereignty play in logistics. The thesis was simple: Amazon is building a stack so complete that once you’re in, leaving becomes structurally expensive. Several people reached out and asked the obvious next question — so what would it actually look like to go all-in?

    Fair question. I run my own infrastructure on Google Cloud. I chose that path deliberately, and I’ve written about why. But intellectual honesty requires stress-testing your own decisions. So here’s the exercise: take a real-shaped business and rebuild it entirely on Amazon’s stack. Not as a hypothetical. As a genuine evaluation of where Amazon is genuinely impressive and where the walls start closing in.

    Meet Ridgeline Services

    To make this concrete, let’s build a company. Ridgeline Services is a 22-person regional facilities management company operating across three metro areas. They handle commercial building maintenance — HVAC, plumbing, electrical, janitorial coordination — for property management firms. They have a small warehouse for equipment and supplies, a fleet of service vehicles, and a growing need for both cloud infrastructure and physical logistics.

    Ridgeline is the kind of mid-market services company that exists in every region of the country. They’re past startup chaos but not yet at enterprise scale. They have real operational complexity — scheduling, procurement, fleet management, customer communication, compliance documentation — and they’re growing fast enough that their current patchwork of tools is starting to crack.

    The question: what happens if Ridgeline rebuilds everything on Amazon?

    Layer 1: Cloud Infrastructure (AWS)

    This is where Amazon’s case is strongest, and it’s not particularly close.

    AWS remains the largest cloud provider by market share. For Ridgeline, the relevant services are straightforward: EC2 or ECS for hosting their job management platform, RDS for their PostgreSQL database, S3 for document storage (inspection reports, photos, compliance records), and CloudFront for their customer-facing portal.

    The honest assessment: AWS is excellent here. The breadth of services is unmatched. If Ridgeline’s CTO wants managed Kubernetes, it’s there. If they need a simple managed database, it’s there. If they want serverless functions for automated notifications, Lambda handles it cleanly.

    Where it gets interesting is AI. Amazon Bedrock gives Ridgeline access to foundation models from Anthropic, Meta, Mistral, and Amazon’s own Nova family through a single API. They could build an AI assistant that reads inspection reports, flags compliance issues, and drafts customer communications — all within their existing AWS environment. Bedrock’s Intelligent Prompt Routing can reduce costs by routing simpler queries to cheaper models automatically.

    Verdict: Genuine strength. AWS for compute and AI infrastructure is a defensible choice for a company like Ridgeline. The lock-in exists at the service level (good luck migrating a complex Lambda architecture to another cloud), but the value proposition is real.

    Layer 2: Procurement (Amazon Business)

    Here’s where the stack starts getting interesting. Ridgeline buys a lot of stuff — HVAC filters, plumbing fittings, electrical components, cleaning supplies, safety equipment, uniforms. Their current process is probably a mess of distributor accounts, local hardware store runs, and someone’s personal Amazon account with a company card.

    Amazon Business replaces all of that with a single procurement platform. Approval workflows so the warehouse manager can’t order without the ops director signing off on purchases above a threshold. Integration with accounting systems through connections to platforms like Coupa and SAP Ariba. Business Prime for free two-day shipping on eligible items. Guided Buying to surface preferred suppliers and products that meet organizational standards. Spend Visibility dashboards that show exactly where money is going across all three metro locations.

    For a 22-person company managing multiple locations, this is genuinely useful. The approval workflows alone solve a real problem — Ridgeline’s ops director currently has no visibility into what each location is ordering until the credit card statement arrives.

    Verdict: Genuinely useful, with a catch. Amazon Business solves real procurement pain for mid-market companies. The catch is that once your approval workflows, supplier preferences, and spend history live inside Amazon’s system, switching costs are high. Not because of a contract — because of accumulated organizational knowledge embedded in a proprietary platform.

    Layer 3: Logistics (Amazon Freight and Supply Chain Services)

    This is the layer that prompted the original sovereignty article, and it’s the one that changed most recently.

    In June 2026, Amazon opened its LTL freight service to all domestic destinations — not just inbound to Amazon facilities. Ridgeline can now use Amazon Freight to move equipment between their three locations, ship palletized supplies from distributors to their warehouse, and deliver materials to job sites. The service includes next-day live pickup for orders placed by 5 p.m., real-time GPS tracking from pickup through delivery, automated appointment scheduling at receiving facilities, and electronic proof of delivery.

    Amazon Supply Chain Services (ASCS), launched in May 2026, goes further. Ridgeline gets access to Amazon’s fleet of more than 80,000 trailers, 24,000 intermodal containers, and 100 aircraft. For a facilities management company that occasionally needs to move heavy equipment between metros or receive bulk supply shipments, this is infrastructure they could never build themselves.

    Companies like Procter & Gamble, 3M, and American Eagle Outfitters have already signed on to ASCS. Peter Larsen, VP of Amazon Supply Chain Services, explicitly compared the play to what AWS did for cloud computing — taking Amazon’s internal infrastructure and selling it to everyone.

    Verdict: Impressive infrastructure, sovereignty risk intensifying. The logistics layer is where the vertical stack thesis becomes most visible. Amazon is now your cloud provider, your procurement platform, and your freight carrier. Each layer is individually competitive. Together, they create an integrated dependency that would be extremely painful to unwind.

    Layer 4: Customer Communication (Amazon Connect)

    Ridgeline’s customer communication is probably a disaster. Property managers call a main office number, someone writes the request on a sticky note, and it may or may not make it to the right technician. For a growing company, this breaks fast.

    Amazon Connect — recently rebranded to Amazon Connect Customer — is AWS’s cloud contact center service. It handles inbound and outbound calls, chat, email, and task routing. In April 2026, AWS expanded the portfolio to include Amazon Connect Decisions for supply chain workflows and announced 29 agentic AI features including pre-built autonomous AI agents that can handle routine customer interactions without human intervention.

    For Ridgeline, this means a property manager calls in, an AI agent captures the issue details, checks technician availability against the scheduling system, and either books the appointment directly or routes to a human dispatcher for complex situations. The system integrates natively with other AWS services — the call transcript goes to S3, the AI processing runs on Bedrock, the customer record updates in their RDS database.

    Verdict: Powerful, and deeply entangling. Connect is a genuinely good contact center product. It’s also the layer where Amazon’s vertical integration becomes most seamless — and most difficult to extract. Your call recordings, AI training data, workflow automations, and customer interaction history all live in the AWS ecosystem. Moving to Twilio or a competing platform means rebuilding every automation from scratch.

    Layer 5: Payments (Amazon Pay and Business Credit)

    This is where the stack gets thinner. Amazon Pay is primarily designed for e-commerce checkout — letting customers pay on third-party websites using their Amazon credentials. It’s supported by more than 720,000 merchants, but it’s fundamentally a consumer checkout tool.

    For Ridgeline, which invoices property management companies for services rendered, Amazon Pay doesn’t solve the core problem. They need accounts receivable, net-30 invoicing, and integration with their accounting system. Amazon’s recent rebrand of “Pay by Invoice” to “Business Credit Account” shows they’re moving in this direction, but the offering is still oriented around purchasing from Amazon, not general B2B invoicing.

    Verdict: Gap in the stack. This is where the Amazon-only thought experiment breaks down for a services business. Ridgeline still needs Stripe or a traditional payment processor for customer invoicing, and QuickBooks or similar for accounting. Amazon hasn’t built the B2B financial layer that would complete the sovereignty loop for a company like this.

    Layer 6: The Integration Tax

    Here’s what you don’t see in any individual product evaluation: the integration tax paid by companies that don’t go all-in on one stack.

    If Ridgeline uses AWS for infrastructure, Amazon Business for procurement, Amazon Freight for logistics, and Amazon Connect for customer communication — those four systems talk to each other with minimal friction. Procurement data flows into spend dashboards that inform logistics decisions. Customer calls trigger workflows that check inventory levels sourced from procurement data. AI models trained on call transcripts improve the automated responses that run on the same cloud infrastructure.

    The moment Ridgeline picks a non-Amazon tool for any layer — say, Twilio for communications or a traditional freight broker for logistics — they inherit an integration burden. APIs to maintain, data to sync, authentication to manage, and failure modes that multiply with each connection point.

    This is the actual mechanism of sovereignty capture. It’s not that any single Amazon service is irreplaceable. It’s that the integrated stack creates compound convenience that makes piecemeal alternatives feel expensive and fragile by comparison.

    Where I Actually Landed

    After walking through this exercise honestly, here’s what I think:

    Amazon wins on logistics and procurement for a company shaped like Ridgeline. The combination of Amazon Business and Amazon Supply Chain Services solves real operational pain that mid-market companies currently address with duct tape and spreadsheets. No other single vendor offers this combination.

    AWS wins on breadth but not uniquely on depth. Google Cloud and Azure are legitimate alternatives for compute and AI. The choice between them is real, not a formality. I chose Google Cloud for my own stack because of Vertex AI’s model garden and the integration with Google’s broader ecosystem. Ridgeline could make a credible case for any of the three.

    The sovereignty risk is real but not uniform. Logistics and procurement lock-in happens through accumulated operational data and workflow dependencies. Cloud lock-in happens through service-specific architectures. Payments is the one layer where Amazon hasn’t closed the loop, which means Ridgeline still needs external financial infrastructure regardless.

    The honest conclusion: building entirely on Amazon is more viable in 2026 than it was even six months ago. The ASCS launch and LTL expansion filled the biggest gaps. But “more viable” isn’t the same as “advisable.” The same operational convenience that makes the stack attractive is the mechanism that makes leaving expensive. You’re not buying services — you’re joining an ecosystem. And ecosystems have gravity.

    That’s not a reason to avoid Amazon’s services categorically. Some of them — particularly ASCS for logistics — are genuinely best-in-class. The discipline is in choosing deliberately: use the layers where Amazon demonstrably wins, maintain alternatives where the switching costs are highest, and never mistake integration convenience for strategic advantage.

    The companies that thrive in this environment won’t be the ones that went all-in on any single stack. They’ll be the ones that understood which layers to rent and which ones to own.



  • When Your Shipping Company Becomes Your AI Company: Amazon’s LTL Freight and the Sovereignty Question Nobody Is Asking

    Vendor sovereignty is the structural principle that no single provider should hold simultaneous visibility into a business’s cloud infrastructure, procurement, shipping, payments, and customer data. Amazon’s expansion into LTL freight — announced June 10, 2026, as part of Amazon Supply Chain Services — completes a vertical stack that makes this question urgent for every business owner.

    The Real Story Behind Amazon’s LTL Freight Play

    Yesterday, Amazon announced that its less-than-truckload freight service is now open to all businesses, shipping to any destination nationwide. The logistics press covered the obvious angles: disruption to Old Dominion and Saia, competitive pricing, 80,000 trailers.

    But here is the story nobody is writing: Amazon is not entering freight. Amazon is completing a vertical stack that should concern every business owner who values operational independence.

    When Your Shipping Company Is Also Your Cloud Provider

    Consider what Amazon now offers a mid-market business. AWS runs your cloud infrastructure. Amazon Business handles your procurement — serving 96 of the Fortune 100 with a platform that processed an estimated $35 billion in gross merchandise volume in 2024, according to Modern Retail. Amazon Supply Chain Services, launched in May 2026 under the ASCS brand, now moves your freight via full truckload, LTL, and intermodal rail across more than 80,000 trailers and 24,000 intermodal containers.

    Add Amazon Pay for payments. Amazon Ads for marketing. And behind all of it, the data infrastructure that connects every transaction, every shipment, every server request back to the same company.

    This is not a logistics announcement. This is a consolidation event. And the question every business owner needs to ask is simple: what happens when one company can see your compute costs, your purchase history, your shipping volumes, and your customer data — all at once?

    The Vertical Stack Nobody Is Mapping

    Here is the Amazon vertical stack as it exists after the June 10, 2026, LTL expansion:

    • Cloud computing: AWS holds roughly 28% of the global cloud infrastructure market as of Q1 2026, according to Synergy Research Group. Your servers, databases, AI workloads, and backups.
    • Procurement: Amazon Business serves over 8 million organizations worldwide. Your office supplies, equipment, MRO inventory, and operational purchases.
    • Freight and logistics: Amazon Freight LTL now ships palletized loads to any destination with real-time GPS tracking, sensor-equipped trailers, and EDI integrations. Your physical supply chain.
    • Payments: Amazon Pay processes transactions across e-commerce. Your revenue flow.
    • Advertising: Amazon Ads has become one of the largest digital ad platforms globally. Your customer acquisition spend.

    Each of these services is excellent on its own merits. The LTL announcement specifically highlights faster transit times and lower costs than traditional providers — Pattern, a global ecommerce accelerator, confirmed that in Amazon’s own press release. That is not the concern.

    The concern is what happens when a single entity holds position across all five layers simultaneously.

    The Sovereignty Question

    Sovereignty is not a buzzword. It is a structural question about who controls your operational data and what they can infer from it.

    When your cloud provider can correlate your server scaling patterns with your procurement volume, your shipping frequency, and your payment processing — they have a composite view of your business that no competitor, no regulator, and frankly no board member possesses. They can see when you are growing before your quarterly report drops. They can see when you are contracting before your suppliers do.

    This is not theoretical. AWS already offers its own data sovereignty frameworks, including the European Sovereign Cloud announced specifically to address concerns about U.S.-headquartered companies having access to European business data. If the concern is significant enough for entire continents to architect around it, it is significant enough for a restoration contractor in Houston or a cold storage operator in California to think about.

    Why I Chose Google Cloud Over AWS

    I run a portfolio of WordPress sites for clients across multiple industries — restoration, luxury lending, healthcare facility management, local media. Every one of those clients generates data that belongs to them, not to me, and certainly not to their infrastructure provider.

    I made a deliberate decision to build on Google Cloud Platform instead of AWS. Not because GCP is categorically better — both are world-class infrastructure. But because Google is not simultaneously my clients’ procurement platform, shipping provider, payment processor, and advertising engine.

    The architecture I use is what I call fortress architecture: isolated VPCs per client, air-gapped environments where one client’s data has zero crossover with another’s, and infrastructure designed so that no single vendor can build a composite profile of any client’s operations. The cloud provider sees compute usage. That is it. They do not see what the client is buying, shipping, selling, or spending on ads, because those functions run through different providers with no data-sharing agreements between them.

    This is not paranoia. This is vendor diversification applied to data exposure — the same principle that any competent CFO applies to banking relationships, any supply chain manager applies to sourcing, and any IT director should apply to infrastructure.

    The Sleepwalk Scenario

    Here is what concerns me about the LTL announcement specifically: it makes the full-stack adoption path frictionless.

    A business already on AWS gets a pitch for Amazon Business. The procurement integration is seamless — same account, same billing, same dashboard. Then Amazon Freight shows up with LTL pricing that undercuts traditional carriers by a meaningful margin, with better tracking technology. Each individual decision is rational. Each individual service is competitive.

    But the aggregate result is that one company now has a multi-dimensional view of your operations that no single vendor should possess. And unlike a consulting firm that might see inside your business temporarily, Amazon has this view in real time, continuously, across every dimension of your operations.

    The restoration contractors I work with are particularly vulnerable to this. They buy supplies through Amazon Business. They might already use AWS for their management software. Now Amazon offers to ship their equipment. At what point does a business owner stop and ask: is the convenience worth the visibility I am granting?

    What Business Owners Should Actually Do

    I am not arguing that Amazon’s services are bad. They are demonstrably good — the LTL service specifically offers next-day live pickup, real-time GPS tracking, and sensor-equipped trailers that most regional carriers cannot match. Jim Ruiz, director of Amazon Freight, was right when he said businesses wanted to use the service more broadly.

    But good services from a single provider create a different kind of risk than good services from diversified providers. Here is what I recommend:

    Map your Amazon exposure. List every Amazon service your business uses — AWS, Amazon Business, any Amazon logistics or shipping, Amazon Pay, Amazon Ads. See the full picture before you add another layer.

    Understand the data correlation risk. Ask yourself: if one company could see all of this data simultaneously, what could they infer about my business that I would not want a competitor, a vendor, or a platform to know?

    Diversify deliberately. You do not need to leave AWS. But if you are on AWS, maybe your procurement runs through a different vendor. If Amazon handles your procurement, maybe your freight uses a carrier that is not connected to your cloud and purchasing data. The goal is to ensure that no single entity can build a composite operational profile.

    Ask the hard question about data walls. Amazon has internal policies about data separation between business units. But policies are not architecture. Policies can change. Architecture — actual infrastructure isolation, different legal entities, separate data stores — is harder to undo. When you evaluate any vendor’s data practices, look at the architecture, not the policy page.

    The Bigger Pattern

    Amazon’s LTL expansion is not happening in isolation. This is part of a broader trend where cloud-native companies extend into physical operations: logistics, payments, hardware, telecommunications. The value is in the data layer that connects all of these services, not in any individual service margin.

    The companies that will maintain operational independence over the next decade are the ones making deliberate infrastructure decisions today. Not the ones that sleepwalked into a single-vendor stack because each individual integration was marginally cheaper or more convenient.

    Convenience is a feature. Sovereignty is a strategy. Know which one you are optimizing for.

    Frequently Asked Questions

    What is Amazon’s LTL freight service?

    Amazon Freight LTL, part of Amazon Supply Chain Services (ASCS), allows businesses to ship palletized loads — typically one to six pallets or 150 to 15,000 pounds — to any destination in the United States. Announced on June 10, 2026, the service is powered by more than 80,000 trailers and 24,000 intermodal containers, with real-time GPS tracking and next-day pickup options.

    What is vendor sovereignty and why does it matter?

    Vendor sovereignty is the principle that no single provider should have simultaneous visibility into your cloud infrastructure, procurement, logistics, payments, and customer data. When one company holds all these positions, they can build a composite operational profile of your business that creates competitive intelligence risk and dependency that is difficult to unwind.

    Why is Amazon’s vertical stack different from other large vendors?

    Most enterprise vendors dominate one or two categories. Amazon is unique in offering cloud computing (AWS, 28% global market share), B2B procurement (Amazon Business, serving 8 million organizations), freight logistics (Amazon Freight), payments (Amazon Pay), and advertising (Amazon Ads) under one corporate entity. No other company spans all five operational layers.

    Should businesses stop using AWS because of this?

    Not necessarily. AWS is world-class infrastructure. The recommendation is to diversify deliberately — if you use AWS for cloud, consider non-Amazon options for procurement, shipping, and payments. The goal is preventing any single vendor from building a multi-dimensional view of your entire operation.

    What is fortress architecture?

    Fortress architecture is a cloud infrastructure design pattern using isolated Virtual Private Clouds (VPCs) per client with air-gapped environments, ensuring zero data crossover between clients and limiting what any single vendor can observe about a business’s operations. It applies vendor diversification principles to data exposure.

    How does Amazon’s LTL service compare to traditional carriers?

    Amazon Freight LTL offers competitive pricing, real-time GPS tracking from pickup through delivery, sensor-equipped trailers, automated appointment scheduling, EDI integrations, and next-day live pickup for orders placed by 5 p.m. Pattern, a global ecommerce accelerator, reported faster transit times and lower costs compared to traditional LTL providers.