Dyrected is now in public beta

Dyrected is now in public beta.

We built it for a problem that kept appearing in different forms: the website was finished, but the handoff was not.

A product team still needed engineering to update marketing copy. A freelancer had become the permanent editor for a client site. Someone had built a website with Lovable or Bolt and discovered that the client could not safely change a sentence without opening the AI builder.

Dyrected gives those websites a structured content layer and a focused editing dashboard.

Developers and builders keep control of the design and content structure. Teammates and clients get access to the content they are responsible for.

Who the beta is for

The public beta is for people who already have a website or application and need to make its content manageable.

That includes:

• Product teams that want marketing and operations to publish without engineering tickets
• Developers adding content management to an existing application
• AI builders using Lovable, Bolt, v0, Cursor, Replit, or Windsurf
• Agencies that need a repeatable client handoff
• Freelancers who want to finish projects without keeping every content update

Dyrected is not a visual website builder. It does not replace your frontend or decide how the website should look.

It sits behind the website and manages the content shown inside the components you already built.

What you can use today

The beta includes the parts needed to create and hand over a structured editing experience:

• Content schemas defined in TypeScript
• Collections for repeatable content
• Globals for shared or single-instance content
• A generated admin interface
• Media management
• Access control
• Hooks for documented content behaviour
• A REST API and type-safe SDK
• Embedded integration for existing applications
• Cloud and self-hosted deployment options

The schema remains with the codebase. A developer can review changes, track them in Git, and keep the content model aligned with the frontend.

Editors work inside the structure without gaining access to the implementation behind it.

A guided setup for AI-built websites

AI website builders made it much faster to create a working site. They did not automatically solve the client handoff.

We have added a detailed [AI-builder setup guide](/guide) for that workflow.

The guide uses one staged prompt rather than asking the AI to install a CMS in one large change.

The prompt inspects the actual website, separates editable content from the interface, turns that work into a plain-language editing plan for approval, reads the current Dyrected documentation, installs the packages, creates the content structure, configures access, and connects the existing design.

Large sites are handled in small verified batches. The user approves what the client should experience without being asked to make technical decisions about fields, collections, globals, access hooks, or APIs.

What public beta means

Public beta means Dyrected is available for real projects, but we are still refining the experience.

Some workflows will need clearer documentation. Some integrations will expose awkward cases we have not encountered yet. Parts of the interface will change as we learn how teams and clients actually use them.

That is why we are opening access now.

We want feedback from people using Dyrected for genuine handoffs, not only test projects. Where did the setup become confusing? Which permissions did your client need? What did your AI builder misunderstand? Which part still required too much technical knowledge?

Those details are more useful than a general feature request.

What we care about during the beta

Our priority is making the path from finished website to safe client editor dependable.

That means improving:

• Setup instructions across different frameworks and AI builders
• Content modelling for real, unconventional websites
• Access control that is understandable without being simplistic
• Clearer editor experiences for clients and non-technical teammates
• Reliable migration from hardcoded content
• Documentation that agents can follow without inventing APIs

We would rather make this core workflow solid than fill the product with unrelated features.

How to start

If you built the website with an AI tool, begin with the [setup prompt guide](/guide). It will help you identify the editable content, approve the handoff, and install Dyrected in verified stages.

If you are integrating Dyrected directly into an application, start with the [developer documentation](https://docs.dyrected.com).

The signup page still lives at the early-access route while we roll beta accounts out. That is where you can create your first Dyrected site.

[Join the Dyrected public beta](/early-access) and tell us where the handoff still feels harder than it should.