Start free. Scale when you're ready.

Yes, genuinely free — no card required, no trial clock. The limits are real: 1 site, 512 MB storage, 2 admin users, and 10,000 API requests per day. There's a small 'Powered by Dyrected' badge in the admin footer. When your project grows past any of those limits, you upgrade. That's the whole model.

That's exactly what Dyrected was built around. Most developer-friendly CMSes end up handing all content edits back to the developer because clients take one look at the interface and give up. Dyrected's admin shows clients only what you defined for them — their collections, their fields, save and publish controls. No schema editor, no config panel, nothing that doesn't belong to them. You control the structure. They control the content inside it.

On the free Maker tier, there's a small 'Powered by Dyrected' badge in the admin footer. On Solo and above it's gone. On the Platform license you get full white-label — your logo, your domain, no mention of Dyrected anywhere in the interface your customers see.

In code. A TypeScript config file that lives in your repository, reviewed in a pull request like any other change, and deployed with your app. There's no browser-based schema editor to click through. If you ask an AI tool to scaffold the config for you, it takes seconds. The schema can't drift out of sync with your codebase because it lives in the same repo.

Yes, that's a common use case. If your AI tool generated a Next.js or Nuxt app, you add the Dyrected package, drop a config file into the project, and on the next deploy your client has an admin at /admin. No separate server to spin up, no new account for them to create, no rebuild required.

Payload and Sanity are excellent tools if your audience is also a developer. Where Dyrected differs: the admin is designed for non-technical clients to use without handholding, the schema is a single TypeScript config file rather than a GUI-based studio, and it embeds into your existing Next.js or Nuxt app as one package with no separate CMS server to maintain. Contentful and similar SaaS platforms lock your content in their cloud. Dyrected doesn't — you can self-host it, move it, or export everything at any time.

Yes. Role-based access control is built in. You define roles in your config and assign them from the admin. A content writer can be scoped to the blog collection only. A marketer gets landing pages but not the changelog. Operations manages FAQs but not pricing. Nobody touches what they shouldn't, and you don't have to police it manually.

On cloud plans, you have a 30-day window after cancellation to export everything. Full JSON export and media downloads are available from the admin at any time — not just when you're leaving. On a self-hosted setup you own the server and database outright, so nothing changes regardless of what happens to our billing relationship.

You can purchase additional storage on top of your plan. We'll notify you before anything breaks so you have time to upgrade.

No. We offer a free tier so you can fully validate Dyrected before committing to a paid plan. If something isn't working as expected, reach out and we'll sort it out.

A site is one Dyrected project — its own collections, globals, and admin users. Each client you build for typically gets one site. If you run a multi-tenant platform and need isolated workspaces per customer, that's the Platform license.

Yes. Building client websites on a self-hosted Dyrected instance is free under the BSL license. You only need a paid cloud plan if you want us to run the infrastructure. The restriction is that you can't resell Dyrected's hosted infrastructure as your own product — that's what the Platform license covers.

The Platform license. It gives you isolated workspaces per customer, white-label admin UI, SSO (SAML 2.0, Okta, Azure AD), and commercial redistribution rights. Pricing is custom based on your tenant count and usage profile. Get in touch and we'll scope it out.