Skip to main content
Contentstack MCP profile hub is in general availability!
Scroll to diveSkip the iceberg ↓

Build vs. buy

Buy the platform, vibe the rest.

AI can build you a CMS in a weekend. So why would you buy one? Scroll down the iceberg to see what building it yourself really means.

The tip of the iceberg

You just want a custom interface.

It seems like this is very easy to build nowadays, but beware…

The waterline

The part you vibe is the small part.

But every app depends on governance, security and scalability.

Below the surface

What you don’t see, or think is easy.

Content models, assets, localization, permissions, workflows, publishing, audit and security. Each one takes years to get right at scale.

The whole iceberg

Build it from scratch and you own all of this.

For years, through every migration, audit and new channel.

The turn

Or don’t. Contentstack is the iceberg.

It’s already built, and it’s run for you. Your apps use it through APIs, the CLI and MCP.

What to build instead

What if you only had to build the tip of the iceberg?

Vibe-code the sites, apps and agents your teams need. The platform underneath stays put and deals with the complicated things.

Why the question is back

For years, buying a content platform was the obvious call. AI changed half of that equation: building got cheap. The other half didn’t move. Here is the short version, then where to split the work.

  1. Then

    Buy, don’t build.

    Building a content platform was slow, expensive and risky. Buying one was the safe call.

  2. Now

    AI builds a CMS in a weekend.

    Content types, an editor, an API. So the question is back: if building is that cheap, why pay for a platform?

  3. But

    Owning it didn’t get cheaper.

    Permissions, workflows, localization, publishing, audit and security take years to get right, and they never stop needing work.

  4. So

    Do both, split in the right place.

    Contentstack runs the governed platform. You vibe-code the Studio pages, apps, tools and agents on top, as often as you like.

  5. Decide

    Build the difference. Buy the foundation.

    Build when the experience is narrow, experimental or genuinely differentiating. Buy when the work is shared, governed, regulated or expected to last for years.

What’s under the waterline

With AI you can cancel a subscription on Friday and have a working CMS by Sunday. Content types, an editor, an API. It’s a good demo.

Then the first real editors arrive, then the second market, then the security review. Skip the platform and you quietly become its database administrator, its security engineer and its on-call rota. None of that got cheaper because version one did.

Read “Buy the plumbing, vibe the rest” →

Build the tip

The tip is where your business is different, so that’s where your time should go. Interfaces are cheap now, and every team can get its own:

  • A narrow editor app for one type of content.
  • An internal tool for one team’s job.
  • An agent that drafts, translates or tags content for a person to approve.
  • Developer workflows in Cursor or Claude Code, through MCP and the CLI.

They all share the same content and rules. That shared part is what you buy.

Build your first Developer Hub app →

The weekend version, and year two

Each of these looks small in the first version. None of them stay small.

  • Content models

    The weekend version

    A few tables and a JSON column.

    Year two

    Schema changes on live content, references across types, and migrations nobody wants to run.

  • Assets

    The weekend version

    An upload folder in object storage.

    Year two

    Transforms, a CDN, usage tracking, and rights that expire in the middle of a campaign.

  • Identity and OAuth

    The weekend version

    One login for the team.

    Year two

    SSO, SCIM, tokens scoped per app and per agent, and access removed the day someone leaves.

  • Permissions

    The weekend version

    Admins and everyone else.

    Year two

    Roles per region, brand and content type, and someone asking who could edit this page last March.

  • Workflows

    The weekend version

    A status field.

    Year two

    Approval chains that differ per market, with legal review that can’t be skipped.

  • Localization

    The weekend version

    A locale column.

    Year two

    Fallback chains, translation vendors, and partly translated entries going live by accident.

  • Publishing

    The weekend version

    A publish button.

    Year two

    Scheduled releases, environments, rollback, and cache that clears everywhere at once.

  • Audit

    The weekend version

    Nothing.

    Year two

    A full history of who changed what and when, because a regulator asked.

  • Security

    The weekend version

    HTTPS.

    Year two

    Pen tests, SOC 2 evidence, data residency and a questionnaire from every new customer.

Build it or buy it?

Build it if

  • It serves one team, one workflow or one channel.
  • It changes often, or you want to try it and maybe throw it away.
  • It’s part of what makes your brand or product feel different.
  • A developer or an agent can build it in days on top of APIs.

Buy it if

  • Every team needs it, and it has to work the same way for all of them.
  • Mistakes are expensive: permissions, approvals, audit, security.
  • It has to keep working for years, through migrations and new channels.
  • Agents will act on it and need rules they can’t get around.

Start building

Pick one small job. Connect your AI tools to a stack, and build the interface for it this afternoon. Contentstack runs everything under the waterline.

Frequently asked questions

  • Why not use a database and an LLM?

    You can, and for a prototype you should. The question is who owns permissions, workflow, localization and audit when that prototype has 400 editors in 30 markets. That work doesn’t shrink because the first version was cheap.

  • Doesn’t building on a platform mean lock-in?

    Your content goes in and out through APIs, the CLI and MCP, and your interfaces are your own code. What you depend on is the governance layer, which is the part you didn’t want to build anyway.

  • What if our teams never use the Contentstack UI?

    That’s fine. It’s the point. Studio is one interface among many. Your own apps, IDEs and agents all work on the same governed platform.

  • What is the total cost of building and maintaining a content platform?

    Include engineering, security, operations, compliance, migrations, support and opportunity cost—not just the first prototype. The ongoing ownership burden is usually the part teams underestimate.

  • When does building your own content platform make sense?

    It can make sense for a narrow workflow, a short-lived experiment or a genuinely differentiated capability, provided the team is prepared to own the operational burden over time.

  • Can we migrate away later?

    Clarify which content and interfaces remain portable through APIs, exports and the CLI, and which governance capabilities are platform-specific. The more your interfaces use standard access paths, the easier future change becomes.