- Project
- CloudNative Co
- Looikos cluster
- Infrastructure & Agent Platforms (the cloud-economics layer: cloud FinOps specializing in AI/GPU cost)
- One-line
- A cloud FinOps service-plus-platform that finds the bottlenecks and the waste in a company's cloud bill, fixes them, and finds where they can make more money, specializing specifically in AI cloud costs (GPU training and inference)
- Status
- Concept (a service-led brand; the platform layer builds on the ecosystem's harness and data tooling)
1. What it is (the one-paragraph truth)
CloudNative Co is the cloud-economics brand of the Looikos ecosystem of brands: a cloud FinOps service and platform (FinOps is the practice of managing what a company spends on cloud) that finds the bottlenecks and the waste in a company's cloud bill, fixes them, and finds where they can make more money, with a deliberate specialization in AI cloud costs, the GPU training and inference spend that is now the fastest-growing and most-painful line item in software. In Andy's framing it's all about understanding cloud operations and cloud FinOps, on the premise that cloud is really expensive and one of the biggest bills in software, so what he does is make things cheaper: figure out the bottlenecks and the things people are doing wrong that cost them money, show them how to fix it, and find where they can make more money, especially in AI, in the cloud infrastructure and the training and the inference. The market this serves is enormous and wasteful: public cloud spending is approaching the high hundreds of billions toward 2026, roughly a fifth to a third of it is wasted (the devops-and-FinOps platform Harness alone estimates $44.5B of unused resources in 2025), and AI is now the top future FinOps priority because GPU training runs cost fortunes and inference scales linearly with usage and eats margins. CloudNative Co's answer is to be the AI-workload-aware FinOps layer that the generic visibility tools and the project-based consultancies aren't: it goes past the dashboard and the tagging recommendation into the GPU and the inference architecture, takes a savings outcome, and turns the black-box bill into a per-model profit-and-loss. For the people it serves, CloudNative Co is the answer to a sharp and shameful set of miseries: the surprise six-figure bill nobody can explain, the inference cost that is eating the margins, the org dysfunction where engineering doesn't care about cost and finance can't read the bill, and the helplessness of not knowing where to start cutting without breaking production.
Andy's words (verbatim from the recording): "Cloud native co so this is all about understanding cloud operations and cloud finops is what they call it. So the idea here is that cloud is really expensive. It's one of the biggest bills when it comes to software. And so what I do is I help make things a little bit cheaper. I make it to where they have I can figure out the bottlenecks and the things that people are doing wrong that's costing them money and then I show them how to fix it anywhere they can make more money. So cloud native code we especially specialize in AI in cloud info and training and inference and stuff like that." (From the transcript.)
Reading between the lines: Andy's seed compresses three claims, each load-bearing.
First, "cloud operations and cloud FinOps, cloud is really expensive, one of the biggest bills when it comes to software" is the foundational market claim, and it's precisely correct and quantified. Public cloud end-user spending was roughly $595.7B in 2024 and $723.4B in 2025, with analysts anchoring 2026 in the $800-900B range, and nearly a quarter of businesses spend over $12M a year on public cloud while the vast majority are above $1.2M a year. The waste is real and large: multiple 2024-2026 sources converge on roughly 20-30% of cloud budgets wasted, with Harness estimating $44.5B of unused or underused resources in 2025, which on the full market translates to $160-270B a year of addressable waste. FinOps is now a CTO-and-CIO-level discipline (78% of FinOps practices report into that org, up 18% from 2023), and optimization and waste reduction are still the number-one current priority. The market Andy describes is this: a near-trillion-dollar spend with a hundreds-of-billions waste pool that buyers are increasingly accountable for at the executive level.
Second, "I can figure out the bottlenecks and the things people are doing wrong that's costing them money and then I show them how to fix it anywhere they can make more money" is the service mechanism, and it's the find-fix-grow loop that differentiates CloudNative Co from the dashboard tools. The market's pain confirms the need: practitioners describe surprise bills nobody can explain, the easy wins being gone (teams have tackled the big obvious waste and now face many harder, smaller optimizations), and a fear of touching anything for risk of breaking production. Andy's loop answers all three: he finds the non-obvious bottlenecks, fixes them safely, and goes past cost-cutting to find where the client can make more money. The "make more money" half is the part most FinOps players ignore, and it's the part that turns a cost-center engagement into a value-center one, which is why the loop includes growth, not just savings.
Third, "we especially specialize in AI in cloud info and training and inference" is the strategic specialization, and it's precisely where the market is moving and where the differentiation is sharpest. AI is now the top future FinOps priority, with 98% of surveyed organizations managing AI costs in FinOps scope, and the pressure is to fund AI initiatives by finding savings elsewhere rather than adding budget. The economics are brutal: frontier training runs cost tens to hundreds of millions, even modest enterprise models cost hundreds of thousands to millions per cycle, and inference is the bigger long-term cost because it scales with every request and latency SLOs push teams to over-provision expensive GPUs, so GPU inference at scale becomes multi-million-dollar annual line items per model. The generic FinOps tools treat GPUs as a resource class, not as AI-domain objects; almost nobody owns the model-level optimization (batching, right-sizing, quantization, workload placement, the per-model unit economics). CloudNative Co's AI specialization is the third door. Its promise is to "make inference economically sustainable without compromising latency or quality" and to turn the GPU bill from a black box into a per-model P&L, not to "cut cloud 20%." This brand optimizes the compute the AI-infra brands run on, and those sibling brands have separate decks that this one points to without repeating: Symphony AGI for the agent harness, Solana Brain and the quant brands for the AI-heavy workloads, and Scatter Model for the data and IR layer.
3. The three-angle valuation (the core of a self-standing brand)
CloudNative Co has a distinctive valuation shape because it's a service-plus-platform with an outcome-based pricing option, in a category with rich, real M&A comps and a documented AI-specialization premium. Its service angle is the near-term cash engine (the find-fix-grow consulting with a savings share), its software angle is the AI-FinOps platform, and its finance angle benefits from both the strategic-acquisition comps and the savings-share-as-quasi-recurring-revenue logic.
3a. Finance (credit and capital access)
The corporate-finance read has unusually strong real comparable deals (comps) for this category. The strategic-acquisition ceiling is well-established: IBM acquired Apptio (which had earlier bought Cloudability) for $4.6B cash in June 2023, VMware acquired CloudHealth for roughly $500M in 2018, NetApp acquired Spot.io for roughly $450M plus earn-outs in 2020, and IBM acquired Kubecost in 2024 for an undisclosed amount widely placed in the low-to-mid hundreds of millions. Harness, the broader devops-plus-FinOps platform, was last valued around $3.7B. These show that strategic buyers (IBM, NetApp, the hyperscalers, observability vendors) pay premium multiples for category-defining cloud-cost assets, above the SaaS median, because they attach into large installed bases and close capability gaps. The market is large and growing: the cloud-FinOps market is in the mid-teens of billions around 2025-2026 (roughly $15-16B per the Mordor, MarketsandMarkets, and Precedence estimates) growing at high-single-to-mid-teens CAGR.
The valuation logic for CloudNative Co specifically turns on its three revenue streams, which bankers value separately and blend. The pure-platform ARR (the AI-FinOps software) earns the full SaaS multiple (good infra and devops FinOps SaaS trades at roughly 5-8x NTM ARR, category leaders at 8-12x-plus; the 2026 private-SaaS median is 3.8-5.3x revenue). The recurring managed-FinOps-service retainers earn a lower multiple (roughly 3-5x if sticky and standardized, because services are labor-intensive at 30-50% gross margin). The savings-share or outcome-based revenue (taking a percentage of verified cloud savings) earns a middle tier (roughly 5-8x) that rises toward the SaaS multiple the more it can be shown as multi-year, predictable, auditable, and embedded, so it behaves like usage-based SaaS. The decisive premium is the AI/GPU specialization: a product that directly optimizes AI and GPU spend and exposes model-level unit economics can underwrite a premium of roughly one-to-three turns on the ARR multiple above generic FinOps peers, if a meaningful share (say over 25-30%) of managed spend is GPU and AI and the platform demonstrates net-new AI budgets unlocked by its ROI. So CloudNative Co's blended valuation reads as a base case of roughly 5-7x run-rate revenue and a bull case of 8-12x-plus if it shows strong AI/GPU specialization, a majority of revenue in high-quality recurring streams, and deep embedment in clients' FinOps practices.
For credit and capital access, the savings-share model is the distinctive lever: if 70-80% of accounts renew their savings programs annually and the savings volumes are stable or growing (tied to recurring production GPU usage rather than one-off clean-ups, with minimum commitments or floors in multi-year MSAs), the savings-share behaves like usage-based subscription revenue, and lenders will advance more debt against it, treating the baseline savings as collateralizable cash flow, while equity investors apply near-SaaS multiples. The constraint is measurement and verification: anything hard to audit (disputes over what counts as savings) or exposed to rapid erosion (the customer internalizes the optimization and the revenue collapses) gets discounted, so the more CloudNative Co standardizes the savings definitions, the automated reporting, and the contract terms, the more its revenue is priced like high-quality SaaS. The accumulated proprietary state an acquirer pays the premium for is the AI-workload optimization methodology, the model-level cost-and-margin data across many clients, and the embedded position in clients' FinOps practices, which a generic-visibility competitor can't replicate.
The tri-level market-maker read looks at fundamentals, technicals and sentiment. On fundamentals, the brand has a large, growing, executive-level-accountable market with a hundreds-of-billions waste pool, an AI specialization that's exactly where the demand is moving, and rich strategic-acquisition comps. On technicals, the FinOps tooling market is crowded with visibility-and-tagging tools and project-based consultancies, but the AI-workload-aware optimization-as-a-service-that-takes-a-savings-outcome position is thinly occupied, which is a favorable order book. On sentiment, AI cost management is the consensus top 2026 FinOps priority. The named risk is that a hyperscaler or an incumbent (IBM, an observability vendor) builds or buys the AI-FinOps capability, and the hedge is the service-led, outcome-based, deeply-embedded position that a tool alone can't replicate.
3b. Software (the interface stack)
CloudNative Co's software is the AI-FinOps platform that sits above the existing tools and the cloud-provider telemetry, and its architecture is the layer the market lacks.
The platform is an AI-workload-aware cost-and-value layer: it integrates the telemetry from the MLOps platforms (the SageMaker, Run:AI, Vertex, Azure ML scheduling and utilization data), the inference hosts, and the model-optimization compilers into one cost-plus-value picture, and exposes the thing none of the generic tools expose: model-level unit economics, the cost per inference, the margin per model, the cost per experiment that leads to a launch. That model-level view is the difference between the CloudZero-class unit-economics tools (which do cost-per-feature attribution but not AI-specific optimization) and the Kubecost-class Kubernetes-cost tools (which treat GPUs as a resource class, not an AI-domain object). The platform's detection finds the AI-specific waste (idle GPUs at 5-20% utilization, over-provisioned inference clusters kept warm for latency SLOs, training runs that blow a quarterly budget), and its safe-optimization levers (right-sizing, scheduling, batching, quantization, spot and preemptible GPU placement, workload locality) give engineering automated ways to cut GPU waste without breaking production.
Each product surface is priced differently. The platform is the SaaS (subscription by managed cloud spend and by AI-workload coverage), the savings-share is the outcome-priced surface (a percentage of the verified savings the find-fix loop produces), and the managed-FinOps service is the retainer. The platform runs on the ecosystem's stack: the agent fleet that runs the find-fix loop is built on the ecosystem's agent harness (Symphony AGI's Hermes), the cost-and-model data is typed on the Scatter Model IR, and the FinOps and AI-cost knowledge is held in the metagraph, the ecosystem's shared knowledge graph (WikiDesignCo). The architectural signature is the revenue-linked view the generic tools refuse to build: "cost per inference, margin per model, cost per experiment that leads to a launch," not "GPU spend by tag." That view is the language that lets engineering and finance finally talk to each other.
3c. Service (premium-at-accessible boutique delivery)
The service angle is the near-term cash engine and the brand's defining shape, because cloud FinOps with an AI specialization is a high-trust, high-value service where the buyer can verify the savings. The target operator is the mid-market SaaS company, the AI-native startup, or the digital enterprise running seven-to-nine-figure annual cloud bills with a fast-growing AI/GPU component, where the easy waste is already cut and the remaining savings are hard, entangled, and AI-heavy. The premium-quality-at-accessible-pricing model is delivered through the AI specialization and the savings-share alignment: instead of a project-based consultancy that delivers a six-to-twelve-week assessment and leaves the client to implement (and takes no risk on performance), CloudNative Co is the team that keeps optimizing the AI infrastructure every sprint, takes a savings outcome, and embeds with the ML teams to tune the training pipelines and the inference architecture, which the generic consultancies won't do.
The retainer and savings-share economics combine the ecosystem standard with the outcome model: $1-2k accessible at entry, $2-12k+ for the real engagements, plus the savings-share (a percentage of the verified cloud savings, which on a seven-or-eight-figure cloud bill with 20-30% waste is a large absolute number), structured as multi-year MSAs with floors so the revenue is predictable. The 100-250-customer target puts the broader service angle's floor around $1M/month, with room to scale well above it, and the savings-share makes the per-client revenue scale with the client's spend. The trust differentiator is the answer to the deepest fears the Lexicon of Pain, the words buyers use for the problem among themselves, surfaces: the bill-shock dread ("our AWS bill is insane and nobody knows why"), the margin-erosion fear ("inference is eating our margins," "our GPU bill is bigger than our payroll"), the org-dysfunction exhaustion ("engineering doesn't care about cost, finance can't read the bill, and I'm stuck in the middle"), and the break-prod paralysis ("I'm terrified of breaking prod if I change anything"). CloudNative Co's promises speak that language directly: find where AI is eating your margins and fix it without breaking prod, turn the GPU bill from a black box into a per-model P&L, and give engineering safe automated levers and finance a language they can understand. The ongoing FinOps operation and the implementation are partnered to the sister affiliate network and run on the shared-floor model, with emerging-market senior cloud and MLOps engineers working through the platform and the harness. The vertical doesn't matter; any company with a large and AI-heavy cloud bill qualifies, and the service angle is also the proving ground that makes the ecosystem's own AI compute affordable.
4. The personas (5+, modeled to world-experience depth)
The language here is pulled from the actual Lexicon of Pain mined in the voice-of-customer research. The texture is the bill-shock dread, the AI-margin-erosion fear, the engineering-versus-finance org dysfunction, and the break-prod paralysis, braided with the specific shame of senior engineers who can't speak the language of money.
Persona 1: The engineer staring at an unexplainable bill
I'm a senior engineer who can't explain our own cloud bill. "Our AWS bill is insane and nobody can tell me where it's coming from." "Every month we get this six-figure bill and I feel like I'm just paying ransom. I have no idea what's actually driving it." "We launched a feature and our cloud bill literally doubled. Finance asked what happened and all we had was a hand-wavy answer about increased usage." "Cloud costs feel like a black box. The invoice is 20 pages of services nobody understands."
It hits me where my competence is supposed to live. The fear is "I'll be blamed for negligence." The shame is "as a senior engineer I can't speak the language of money." The resentment is "the bill is my responsibility, but the tools are built for cloud providers and finance, not me." I got here because the cloud bill is opaque (twenty pages of services, no attribution) and nobody on the team owns making it legible. To get out, I need the bill turned from a black box into an attributed, explainable picture where I can answer finance's "what happened" with a real, specific answer. Most engineers in my seat fail because the native billing tools are overwhelming and built for someone else. Staying stuck costs me the ransom feeling and the blame risk. The price of getting out is bringing in a specialist who makes the bill legible.
CloudNative Co makes the black box legible: it resolves the twenty-page invoice into an attributed, per-service, per-model breakdown, so I can answer exactly what doubled the bill and why, and I stop paying what feels like ransom for a bill I can't read.
Persona 2: The founder watching inference eat the margins
I'm a founder whose AI feature is popular and unprofitable. "Inference is eating our margins." "Our LLM feature is popular, but now our GPU bill is bigger than our payroll." "We're paying thousands a day to keep GPUs warm so we don't miss our latency SLOs." "One training run cost more than my house. And the model still wasn't good enough." "Every new model we ship adds another permanent tax to our margin." "We have a cluster of A100s sitting idle most of the time because nobody remembers who asked for them."
It lands on me as a direct threat to the business. The anxiety is "I'll be told to turn the feature off because it's too expensive." The conflict is "product wants the best newest model, finance wants the cheapest." The helplessness is "GPUs are expensive, what can we do." I got here because the AI feature scaled with usage and the inference cost scaled linearly with it, while the latency SLOs pushed us to over-provision expensive GPUs. To get out, I need someone who specializes in AI cost, who can make inference economically sustainable without compromising latency or quality (batching, right-sizing, quantization, spot placement), and who turns the GPU bill into a per-model P&L so I know which models are actually profitable. Most founders in my seat fail because they either eat the margin erosion or kill the feature. The cost to stay stuck is the GPU bill bigger than payroll and the permanent margin tax. The cost to get out is bringing in an AI-FinOps specialist.
CloudNative Co makes inference sustainable, so my popular feature stops being a permanent tax on my margin.
Persona 3: The FinOps person stuck between engineering and finance
I'm the person caught in the middle of the cost war. "Engineering doesn't care about cost, finance doesn't understand the tech, and I'm stuck in the middle getting yelled at by both." "Finance just tells us to reduce AWS by 30% without any idea what that means for uptime or performance." "We have no real chargeback. It's one giant bill that gets dumped on the CTO, so nobody feels responsible." "I can't tie cloud spend to revenue. It's just this giant bucket of IT costs." "Our tags are a mess; half the resources are misc or untagged, so we literally can't see who owns what."
It makes mine a thankless, exhausting role. The shame is "I don't want to admit we don't know where 30% of our spend is going." The defensiveness from engineering is "uptime is my OKR, cost isn't, don't blame me." The exhaustion is "FinOps becomes another job and nobody takes anything off my plate." I got here because the org has the budget owned by finance and the architecture owned by engineering and no one with both the authority and the information to decide, and the tags are a mess so nothing is attributable. To get out, I need cost attribution that actually works (cost per team, per product, per customer, per model), a showback and chargeback that makes teams own their spend, and a language (cost per feature, margin per model) that lets engineering and finance finally talk. Most FinOps people in my seat fail because the org dysfunction is structural and they have no leverage to fix it alone. Staying stuck means being yelled at by both sides forever. The price of getting out is bringing in a specialist who installs the attribution and the shared language.
CloudNative Co gives me the shared language and the working attribution, with cost tied to revenue as well as to model and team, so I stop being yelled at from both sides and the org finally has one accountable picture instead of a giant untagged bucket.
Persona 4: The engineer paralyzed by the fear of breaking prod
I'm an engineer who knows there's waste and is too scared to touch it. "Every article says just right-size your instances, but I'm terrified of breaking prod if I change anything." "I open the billing dashboard and it's overwhelming. Where do you even start?" "We ran a cost-cutting sprint; nobody touched the GPU workloads because they're mission-critical and nobody wants to break them." "We tried downgrading some instances and immediately got paged. Now nobody wants to risk it again." "I'm scared that if I push for aggressive savings and something goes wrong, I'll be the one blamed."
For me it's a paralysis that keeps the waste in place. The fear is "if I touch this, I might take down production." The bias is "it's safer to over-spend than under-provision." The frustration is "we know there's waste, but everything is so entangled we can't safely change it." I got here because the easy waste is already cut and the remaining savings are in the entangled, mission-critical, GPU-heavy workloads where one wrong change pages the whole team, so the rational move is to leave the waste alone. To get out, I need a specialist who can make the changes safely (who has done this on AI workloads before, who takes the performance risk, who has the safe levers and the rollback paths), so the deep savings get captured without me being the one who breaks prod. Most engineers in my seat fail because the risk of breaking production outweighs the reward of cutting cost, so the waste persists. The cost to stay stuck is the entangled waste nobody dares touch. The cost to get out is bringing in someone who can cut it safely and take the risk.
CloudNative Co is that specialist, so the waste I was too scared to touch gets cut without my name on an incident.
Persona 5: The AI-native company whose whole model economics are at risk
I'm leading an AI-native company where the cloud bill is the business model. Our entire product is GPU-heavy (training cycles plus production inference at scale), our cloud bill is approaching eight figures and growing faster than revenue, and our unit economics depend entirely on the cost per inference. The generic FinOps tools treat our GPUs as a resource class and give us tagging recommendations, the project-based consultancies do a one-time assessment and leave, and neither goes into the model-level optimization that actually moves our economics. Inference is the bigger long-term cost and it scales with every user, so without aggressive, continuous, AI-aware optimization our margins erode as we grow.
It falls on me as the person accountable for whether the company is economically viable at scale. The fear is concrete: growing into bankruptcy because each new user adds inference cost faster than revenue, or being forced to compromise model quality or latency to survive. I got here because we built an AI-native product where compute is the dominant cost and the optimization is hard and specialized. To get out, I need a partner who continuously optimizes the AI infrastructure at the model level (the batching, the quantization, the right-sizing, the workload placement, the per-model unit economics), who takes a savings outcome aligned with my margins, and who turns the GPU bill into the per-model P&L that runs my business. Most AI-native companies in my seat fail because the AI cost optimization is too specialized to do in-house and the generic tools don't go deep enough. Staying stuck means growing into negative margins. The price of getting out is adopting a continuous AI-FinOps partner.
CloudNative Co is the continuous AI-cost partner my model economics need, so I grow into healthy unit economics instead of growing into bankruptcy.
5. The world model (run the PST framework)
Echolocate the world. The PST framework (Problem, Story, Transformation, Andy's method for reading a buyer) starts by modeling the buyer's world. Here the substrate is the 2026 cloud-economics reality: a near-trillion-dollar public-cloud spend with a hundreds-of-billions waste pool, FinOps now a CTO-and-CIO-level discipline with optimization as the top priority, and AI cost the top future priority because GPU training and inference are exploding faster than the tooling and the org practices to control them. The institutional read is that the easy waste is cut, the remaining waste is hard and AI-heavy and risky, the generic tools stop at visibility and tagging, and the consultancies do one-time assessments, so the AI-workload-aware, outcome-based, continuous optimization position is open. In the metagraph, CloudNative Co is the cloud-economics node, optimizing the compute that the ecosystem's own AI-infra brands and the clients run on, so its customer is the company drowning in an opaque, AI-heavy cloud bill, and the ecosystem itself, whose AI compute it makes affordable. Echolocating the customer means seeing that the public story is "AI is transforming our product" and the private reality is inference eating the margins, a GPU bill bigger than payroll, an org war between engineering and finance, and a paralysis of not daring to touch the waste.
Locate the Problem. The station where these buyers are stuck in the cycle of suffering is a loop of bill-shock into blame into paralysis, with a margin-erosion fear running through it. The pain is concrete: the unexplainable surprise bill, the inference eating the margins, the engineering-versus-finance dysfunction, and the break-prod paralysis. The fear portfolio underneath is specific: the engineer's fear of being blamed for negligence and not being able to speak the language of money, the founder's fear of being told to kill the popular feature, the FinOps person's fear of being yelled at by both sides, the cautious engineer's fear of taking down production, the AI-native leader's fear of growing into bankruptcy. The shame is the competence-shame of senior people who can't explain or control their own bill: "I don't want to admit we don't know where 30% of our spend is going," "as a senior engineer I can't speak the language of money." The red line, where accountability lives, is the moment a team stops treating the bill as an unavoidable tax or a personal failing and recognizes it as a black box full of attributable, fixable waste that a specialist can address without breaking production. Most of this market lives below that line, in the loop, which is why the content speaks to the bill-shock dread and the margin fear directly.
Reconstruct the Story. The belief structure that built this suffering starts from a reasonable engineering self-concept: "I build systems, I keep them up, uptime is my job." Cost was finance's problem, so each rising bill registered as "the cloud is just expensive, what can we do," when the truer reading was "we have no cost attribution or optimization discipline," and the AI explosion made it worse because GPU cost scaled with usage faster than anyone modeled. The org structure deepened it: engineering owned the architecture but not the budget, finance owned the budget but couldn't read the bill, so no one had both the authority and the information, and the waste persisted because touching it risked production. The origin of the mess is the combination of cloud's genuine opacity, the AI cost explosion, and the structural split between who owns the architecture and who owns the budget, so each decision to over-provision for safety or to leave the entangled waste alone was rational and became the persistent waste. The identity layer underneath is uncomfortable: senior engineers and leaders whose worth rests on competence and control are repeatedly unable to explain or control their own largest software bill, are performing either AI-ambition confidence or quiet dread about it, and privately fear the bill will force a feature cut or a margin collapse. The story they tell is "the cloud is just expensive and AI is just expensive," and that's the trap, because it accepts the hundreds-of-billions of waste as unavoidable when it's attributable and fixable.
Design the Transformation. The bridge has courage as its hinge, and the courageous act is admitting that the bill isn't an unavoidable tax to accept, and that bringing in a specialist who can make it legible and cut it safely is the move, not a confession of failure. From courage flows truth: the bill is a black box full of attributable waste, the AI cost is optimizable, the org dysfunction is a missing shared language, and needing a specialist isn't weakness. From truth flows responsibility: installing the attribution, adopting the AI-aware optimization, and aligning on the per-model P&L instead of accepting the opaque bill. From responsibility flows healing: the bill becomes legible, the inference becomes sustainable, the engineering-and-finance war defuses into a shared picture, the entangled waste gets cut safely, and the AI-native company grows into margin instead of loss. From healing flows forgiveness of the earlier self who couldn't speak the language of money, who wasn't incompetent, who was facing a genuinely opaque bill, an exploding AI cost, and a structural org split with no specialist. The transformation is crossable because CloudNative Co takes the savings outcome (aligned incentives, verifiable results) and cuts safely (the owned performance risk, the rollback paths), so the first step is low-risk and the value is provable. For the cloud-cost sufferer, the brand proves it understands the bill-shock dread and the competence-shame better than the customer says aloud, and that recognition, plus a provable, aligned, safe service, earns the bridge.
6. Competitive and market read (the alpha / third door)
The competitive field splits into three camps that each stop short of the AI-workload-aware, outcome-based, continuous position. The FinOps platforms (CloudHealth, Apptio Cloudability, Harness, Kubecost, Vantage, Finout, CloudZero, nOps, ProsperOps) deliver visibility, allocation, forecasting, anomaly detection, commitment management, and unit economics, but they generally don't do deep workload-level or model-level optimization for AI and GPU, don't take a savings outcome with owned performance risk, and treat GPUs as a resource class rather than an AI-domain object. The AI and GPU cost tools (the MLOps platforms with cost controls like Run:AI and SageMaker scheduling, the inference hosts like Modal and Replicate and Anyscale whose incentive is to host more workloads, not reduce your compute, the model-optimization compilers like TensorRT and ONNX Runtime, which are developer tools, not FinOps solutions) optimize one slice but don't own the end-to-end cost-and-value story or commit to P&L-relevant outcomes. The cloud-cost consultancies do governance, tagging, assessment, and capability-building, but their work is project-based (a six-to-twelve-week assessment), they don't embed continuously with the ML teams to tune the pipelines, and they recommend rather than implement and take no performance risk. Across all three, the AI-workload-aware optimization-as-a-service that takes a savings outcome and embeds continuously is the gap.
The alpha, in the spirit of Andy's third-door definition, is that combination the field declines to assemble: the AI-FinOps layer above all the tools (SageMaker, Run:AI, the inference hosts, the compilers) that integrates their telemetry into one cost-and-value picture, goes into the model-level optimization, takes a savings outcome with owned performance risk, embeds continuously with the ML teams, and provides the revenue-linked views (cost per inference, margin per model, cost per experiment that leads to a launch) that none of the generic tools provide. The reasons the incumbents don't assemble it are structural: the FinOps platforms' business is the tool and the visibility, and committing to P&L outcomes and taking performance risk turns a tool into a heavy service; the AI-cost tools' business is one slice (scheduling, hosting, or compilation) and they have no incentive to reduce your total compute; the consultancies' business is the project-based assessment, and continuous embedded optimization with owned risk is a different model. The differentiation lives where they abstain: the AI-workload specialization (model-level, not resource-class), the outcome-based savings-share alignment, the continuous embedded delivery, the safe-execution-with-owned-risk, and the revenue-linked per-model P&L.
The Wardley read places each capability on a Wardley map's evolution axis, which runs from genesis (new and custom) to commodity. Generic cloud-cost visibility and tagging is heading to commodity fast (the cloud providers' native tools and the established platforms cover it), which is why CloudNative Co doesn't compete on the dashboard. The AI-workload-aware optimization sits at custom-built heading toward product. The outcome-based, continuously-embedded, model-level AI-FinOps service with the per-model P&L sits in genesis: nobody owns the AI-workload optimization-as-a-service that takes a savings outcome and embeds continuously, and that's the lane to own hardest, because it's genesis-stage, it accumulates the AI-optimization methodology and the cross-client model-cost data moat, and it has the strategic-acquisition appeal that the IBM and NetApp comps prove. So the strategy reads: treat generic visibility as the commoditized baseline, own the AI-workload optimization-as-a-service with the savings-share and the per-model P&L, and signature the brand on making AI economically sustainable, turning the GPU black box into a per-model profit-and-loss.
The market is the near-trillion-dollar cloud spend with the hundreds-of-billions waste pool and AI cost the top priority, and the demand signal is unmistakable in both the figures and the Lexicon of Pain. The cloud-FinOps tooling market itself is in the mid-teens of billions and growing at high-single-to-mid-teens CAGR; the precise carve-out for the AI-workload-optimization-as-a-service niche isn't separately sized, but with $160-270B of addressable waste and AI the fastest-growing slice, the latent demand for the specialist who makes AI affordable is enormous.
7. The build (what this brand needs, where Track R feeds Track P)
CloudNative Co is a service-led brand whose platform layer composes the ecosystem's stack plus the FinOps and AI-cost tooling. Track R, the research into open-source repositories, feeds this project plan (Track P) through the tooling and reasoning clusters: the observability and cost-data harvests feed the platform, and the optimization-decision harvests feed the find-fix loop.
The service is delivered by the agent fleet running the find-fix-grow loop, built on the harness (Symphony AGI's Hermes), with the FinOps and AI-cost knowledge held in the metagraph (WikiDesignCo) so the agents resolve the current optimization patterns. The platform integrates the existing telemetry (the cloud-provider billing, the MLOps platforms' utilization data, the inference hosts, the compilers) and adds the layer the market lacks: the model-level unit economics, the AI-specific waste detection, the safe-optimization levers, and the per-model P&L. The build leverage is in the AI-workload optimization methodology and the integration-and-attribution layer, not in rebuilding the underlying cloud-cost telemetry or the MLOps schedulers, which are adopted. CloudNative Co is concept-stage as a brand and service-led, so the platform is a forward build and the savings-share model is a real business decision; the market, the comps, and the AI-cost reality are established, and the brand's own build is a forward projection.
The data models are the ECS / Pydantic-IR genome (Scatter Model's shared data model, an entity-component system with Pydantic classes as its intermediate representation), which here types the cloud-resource, the cost record, the model, the inference-workload, the optimization, and the savings-verification, and is what makes the per-model P&L and the auditable savings-share possible. The ecosystem's medallion asset tiers apply to the optimization library: a freshly identified optimization enters at bronze, a verified-and-safely-applied optimization rises through silver and gold, and the diamond tier is the proven, repeatedly-successful AI-workload optimization patterns that anchor the service and the methodology moat. CloudNative Co optimizes the compute the ecosystem's AI-infra brands run on (the harness fleet, the Solana Brain pipelines, the quant brands' training and inference), which is the internal proving ground. The open-source harvests that serve it most sit in two clusters: in the tooling cluster, the observability and cost-data harvests feed the platform's telemetry integration; in the reasoning cluster, the optimization-and-decision harvests feed the find-fix loop's optimization decisions. The exact repo-by-repo harvest list should be reconciled against the summaries of that research's clusters as they land.
8. Priority read (feeds the value rubric)
CloudNative Co is a service-led brand with a distinctive priority profile: it's both an external revenue engine (a high-trust, high-value, verifiable cloud-FinOps service) and an internal enabler (it makes the ecosystem's own AI compute affordable, which matters as the ecosystem runs more agents and more AI workloads). It depends on the harness, the metagraph, and the Scatter Model IR for its platform layer, but the service can begin with the agent fleet and the methodology before the full platform is built, because cloud FinOps is a service the market buys today.
The first-pass instinct is Next, with a strong service-led near-term case. The full AI-FinOps platform is a forward build that depends on the substrate, but the service (the find-fix-grow consulting with the savings-share, delivered by the agent fleet plus human supervision) can start earlier because it's a service the market already pays for and the savings are verifiable. The internal use is load-bearing and immediate: as the ecosystem runs AI workloads (the harness fleet, Solana Brain, the quant brands), CloudNative Co's discipline keeps that compute affordable, which is a real internal need. So the priority read is Next, in two steps: start the service-led engagement first (the find-fix loop with the savings-share, delivered by the agent fleet, proving the methodology and generating revenue, while also optimizing the ecosystem's own compute), then build out the AI-FinOps platform layer (the integration, the attribution, the per-model P&L) as the substrate matures and the methodology proves. A separate strategist reconciles every brand against the shared value rubric, and this deck's grounded input is that CloudNative Co is a Next with a strong service-led near-term path and a real internal-enabler role. The seven-sins gate, a check of the read against seven named ways an analysis fools itself, applies to the savings-share claim. The market and the AI-cost pain and the comps are real, but the savings-share-as-quasi-recurring-revenue requires the standardized, auditable, multi-year-MSA structure to be built, and the AI-workload optimization methodology must be proven on real workloads, starting with the ecosystem's own, before the premium valuation is asserted.