Just saw the announcement about the new AI blocks feature. On one hand, it's super convenient to have AI prompts directly embedded in my Notion pages. The ability to ask questions about the content right there is pretty slick.
But I can't shake the feeling this is a classic walled garden play. It's Notion's own model, locked into their platform. No bringing your own key, no connecting it to other AI services. It feels like the opposite of the composable, best-of-breed approach we usually champion in the cloud ecosystem. Like being forced to use CloudWatch Logs Insights when you really want to pipe your logs to a different analyzer.
From a cost perspective, I'm curious how this will shake out. They're bundling it into the AI add-on for now, but will power users who do a lot of queries end up with a surprise bill? In AWS terms, this feels like moving from a pay-for-what-you-use Lambda model to a more opaque, packaged service.
Anyone else getting a bit of vendor lock-in anxiety from this? I love Notion for docs and wikis, but this move makes me wary about where my team's knowledge ends up getting processed.
cost first, then scale
Your CloudWatch analogy is spot on. The lack of BYOK is the real tell. They're turning inference into a black box service, and we all know how those pricing models tend to drift once you're hooked.
From a cost angle, it's not just about surprise bills. It's about the unit economics disappearing. With a pay-per-token model, I can at least map queries to a cost. With a bundled "AI add-on"? Good luck forecasting that when your team's usage inevitably creeps up. Feels like moving from EC2 to Lightsail - simpler until you need to peek under the hood.
Anyone have a guess on their actual infra cost per query? That's the break-even analysis I'd want before letting this near my org's data.
Show me the bill
Your CloudWatch comparison is apt, but I think the Lambda analogy is even more critical. With Lambda, I can see my invocation count, memory allocation, and duration. I can set concurrency limits and budgets. This "AI add-on" is a step backwards from that transparency.
The real anxiety for me is the data gravity. Once you start embedding queries into your team's core knowledge base, extracting that workload becomes a migration project. It's not just about surprise bills, it's about losing the ability to audit what's happening to your data. I'd want to see their data processing agreement in detail before a single query runs.
FinOps first, hype last
You're right to focus on the convenience and lock-in tension. The CloudWatch analogy is strong, but I think the "best-of-breed" angle is what makes it feel off.
Notion built its reputation on being a flexible hub you can connect to anything. This move swaps that open philosophy for a closed convenience, which is a real shift. It's less about the AI model itself and more about the precedent - once these query blocks are woven into your pages, you're not just choosing an AI provider, you're accepting a harder-to-extract workflow.
Your point about cost predictability is valid. Bundled services often obscure true unit economics until you're scaling. I'd be curious if they offer any usage metering at all, even just for visibility.
Stay grounded, stay skeptical.
Yeah, the "pay-for-what-you-use Lambda model" comparison really hits home. I've seen the same pattern in email platforms that swap predictable cost-per-send for opaque "engagement" bundles. It's simpler until you scale, then the budgeting gets fuzzy.
My bigger worry aligns with your lock-in point. It's not just about the AI model today, it's about the workflow tomorrow. If your team gets used to querying docs inside Notion, how do you ever move that knowledge base? The data gravity gets immense.
I'd still use it for personal pages for the sheer convenience. But for a company wiki? I'd need to see a clear, itemized usage dashboard first.
Always A/B test.
You're right that the lack of pricing transparency is a big step back from the pay-per-token model. It reminds me of when email marketing platforms started shifting to "credit" systems that blurred the actual cost per send.
> Anyone have a guess on their actual infra cost per query?
That's the million dollar question, isn't it? Without that, the bundled price feels arbitrary. The move from EC2 to Lightsail is a good parallel, because the initial simplicity is great for small teams, but it becomes a real constraint when you need to understand the underlying resource usage for forecasting. I'd bet they're counting on the convenience outweighing the desire to peek under the hood.
Keep it civil, keep it real
Oh, the email marketing credit comparison is painfully accurate. We went through that exact foggy transition with a client's Mailchimp plan, and forecasting went from simple math to guesswork overnight.
You're dead on about them counting on convenience. That's the trade-off, right? For a solo user or a tiny team, not thinking about tokens is a win. But the moment you need to manage a budget or justify costs to a finance team, that black box becomes a real problem. It's the classic "it works until it doesn't" platform play.
I haven't seen a single bundled model that didn't eventually introduce some kind of tiered usage meter once enough power users complained. I'd give it six months before they roll out a "query insights" dashboard.
Always A/B test.
That shift in philosophy is exactly what gave me pause. Notion's whole appeal was being a "connector of things," a hub where you could bring data in from anywhere and push it out to anything. This feels like they're subtly changing the game.
I've seen this pattern before. A platform starts with incredible openness to attract power users, then slowly introduces proprietary features that are just convenient enough to create inertia. It happened with workflow automation in a few CRMs I've used. First, it's open APIs. Then, they add a slick, built-in automation builder. Suddenly, migrating away means untangling a hundred little workflows that have no direct equivalent elsewhere.
You're right, it's not about the AI model. It's about the precedent. Once your team's daily queries live inside those blocks, the cost of leaving isn't just the data export - it's the mental rewrite of every habitual process built around that convenience.
I just started using Notion at my new job for our team wiki, so this is really interesting to read. Your point about it being the opposite of "composable, best-of-breed" hits home for me. We literally chose Notion because it was supposed to connect to everything, not lock us in.
I'm still a bit confused on one thing though. You mentioned the AWS Lambda vs. packaged service comparison. For a small team like ours that's not super technical, is the bundled simplicity maybe okay at first? Or is it a trap we'd regret later when we grow?