Running an AI-native business in 2026 means making a decision about infrastructure that most operators don’t realize they’re making. You can run AI operations reactively — open Claude, do the work, close the session, repeat — or you can build an infrastructure layer that makes every session faster, more consistent, and more capable than the last.
We chose the second path. The stack is Google Cloud Platform for compute and data infrastructure, Notion for operational knowledge, and Claude as the AI intelligence layer. Here’s what that combination looks like in practice and why each piece is there.
Why GCP
Google Cloud Platform provides three things that matter for an AI-native content operation: scalable compute via Cloud Run, AI APIs via Vertex AI, and data infrastructure via BigQuery. All three integrate cleanly with each other and with external services through standard APIs.
Cloud Run handles the services that need to run continuously or on demand without managing servers: the WordPress publishing proxy that routes content to client sites, the image generation service that produces and injects featured images, the knowledge sync service that keeps BigQuery current with Notion changes. These services run when triggered and cost nothing when idle — the right economics for an operation that doesn’t need 24/7 uptime but does need reliable on-demand availability.
Vertex AI provides access to Google’s image generation models for featured image production, with costs that scale predictably with usage. For an operation producing hundreds of featured images per month across client sites, the per-image cost at scale is significantly lower than commercial image generation alternatives.
BigQuery provides the data layer described in the persistent memory architecture: the operational ledger, the embedded knowledge chunks, the publishing history. SQL queries against BigQuery return results in seconds for datasets that would be unwieldy in Notion.
Why Notion
Notion is the human-readable operational layer — the place where knowledge lives in a form that both people and Claude can navigate. The GCP infrastructure handles compute and data. Notion handles knowledge and workflow. The division of responsibility is clean: GCP for machine-scale operations, Notion for human-scale understanding.
The Notion Command Center — six interconnected databases covering tasks, content, revenue, relationships, knowledge, and the daily dashboard — is the operational OS for the business. Every piece of work that matters is tracked here. Every procedure that repeats is documented here. Every decision that shouldn’t be made twice is logged here.
The Notion MCP integration is what makes Claude a genuine participant in that system rather than an external tool. Claude reads the Notion knowledge base, writes new records, updates status, and logs session outputs — all directly, without requiring a manual transfer step between Claude and Notion.
Where Claude Sits in the Stack
Claude is the intelligence and orchestration layer. It doesn’t replace the GCP infrastructure or the Notion knowledge base — it uses them. A content production session starts with Claude reading the relevant Notion context, proceeds with Claude drafting and optimizing content, and ends with Claude publishing to WordPress via the GCP proxy and logging the output to both Notion and BigQuery.
The session is not just Claude doing a task and returning a result. It’s Claude operating within a system that provides it with context going in and captures its outputs coming out. The infrastructure is what makes that possible at scale.
What This Stack Enables
The combination of GCP infrastructure and Notion knowledge unlocks operational capabilities that neither provides alone. Content can be generated, optimized, image-enriched, and published to multiple WordPress sites in a single Claude session — because the GCP services handle the technical distribution and the Notion context provides the client-specific constraints that govern each site. Knowledge produced in one session is immediately available in the next — because BigQuery captures it and Notion stores the human-readable version. The operation runs at a scale that one person couldn’t manage manually — because the infrastructure handles the mechanical work while Claude handles the intelligence work.
What This Stack Costs
The honest cost picture: GCP infrastructure at our operating scale runs modest monthly costs, primarily driven by Cloud Run service invocations and Vertex AI image generation. Notion Plus for one member is around ten dollars per month. Claude API usage for content operations varies with session volume. The total monthly infrastructure cost for the stack is a small fraction of what equivalent human labor would cost for the same output volume — which is the point of building infrastructure rather than hiring for scale.
The GCP + Notion + Claude stack is advanced infrastructure. We consult on the architecture and can help design the right version for your operation’s scale and requirements.
Tygart Media built and runs this stack live. We know what the implementation actually requires and where the complexity is.
Frequently Asked Questions
Do you need GCP to run an AI-native content operation?
No — GCP is one infrastructure option among several. The core stack (Claude + Notion) works without any cloud infrastructure for smaller operations. GCP becomes valuable when you need reliable service infrastructure for publishing automation, image generation at scale, or data infrastructure for persistent memory. Operators starting out don’t need GCP; operators scaling up often find it the right addition.
How does Claude connect to GCP services?
Claude connects to GCP services through standard REST APIs and the MCP (Model Context Protocol) integration layer. Cloud Run services expose HTTP endpoints that Claude calls during sessions. BigQuery is queried via the BigQuery API. Vertex AI image generation is called via the Vertex AI REST API. Claude orchestrates these calls as part of a session workflow — fetching context, generating content, calling publishing APIs, logging results.
Is this architecture HIPAA or SOC 2 compliant?
GCP offers HIPAA-eligible services and SOC 2 certification. A “fortress architecture” — content operations running entirely within a GCP Virtual Private Cloud with appropriate data handling controls — can be configured to meet healthcare and enterprise compliance requirements. This is an advanced implementation beyond the standard stack described here, but it’s achievable within the GCP environment for organizations with those requirements.
Leave a Reply