TessryxDocs

How Tessryx works

The mental model: you and your agent, the two surfaces, and the path from idea to live site.

Most tools make you choose: a CMS that's easy but can't do much, or a developer platform that can do anything but needs a developer. Tessryx collapses that choice by splitting the work between two people, you and an AI agent, and giving each of you the surface that fits.

#Two surfaces over one system

Everything in Tessryx exists once, but you can touch it two ways:

  • The build surface is where your agent works. Connected over a standard link (MCP, see Connect your agent), it creates the moving parts of your app: the shape of your data, the logic that renders pages, the public URLs, the integrations. This is the powerful, technical layer.
  • The control surface is where you work: the Tessryx web app. It's a set of visual editors, generated automatically from what your agent built. You edit content in forms, review changes, publish, and manage your domains, team, and settings. No code, ever.

The important part: these aren't two copies that can drift. They're the same objects seen from two sides. When your agent designs a "product" with a name, price, and photo, you get a form with a name field, a price field, and an image uploader, because the form is that design. Change the design, the form changes with it.

#The path from idea to live

A typical project moves through these stages. Your agent drives the building; you drive the decisions.

  1. Describe the outcome. Tell your agent what you want: the pages, the data, the behavior. Be as vague or specific as you like; you can refine as you go.
  2. The agent builds it. It assembles the building blocks (data schemas, content, rendering logic, public endpoints) and can preview the result privately before anything is public.
  3. You review and edit. Open the content editors and make it yours: fix the copy, swap the images, adjust the data. This is the part you own day-to-day.
  4. Publish. Going live is a deliberate step: drafts cost nothing and stay private until you (or your agent) publish the version you intend.
  5. Connect your domain. On a paid plan, point your own domain at the site; it serves from your address, indexed by search engines, with no Tessryx badge. See Custom domains.
  6. Keep it running. Content changes in the editors, integrations pull from other systems, and scheduled jobs keep data fresh, all without rebuilding anything.

#What you never have to do

  • Set up infrastructure. There are no servers, containers, or deploy pipelines. Hosting, caching, and TLS certificates are handled.
  • Learn a framework. You describe outcomes; the agent handles the implementation.
  • Wait for a developer to change a word. Content lives in editable forms that anyone on your team can use.

#Where to go next