The building blocks
A plain-English tour of the pieces your agent works with, so you can follow what it built.
Everything on Tessryx is assembled from a small set of parts. Your agent works with these directly; you mostly touch their friendly side, the content editors. Knowing what each piece is makes what your agent built legible.
| Piece | In one line | You touch it as… |
|---|---|---|
| Schema | The shape of a kind of data | The form fields you fill in |
| Content record | One actual item of that data | An entry in an editor |
| Workflow | The logic that turns data into a page or response | (Usually the agent's job) |
| Endpoint | A live public web address | The URL your visitors hit |
| Schedule | A workflow that runs on a clock | An automation you switch on/off |
| Integration | A connection to an outside system | A secret you set the key for |
| App | A group of the above, edited as one unit | Your project |
| Domain | Your own address for a site | Your URL |
This page is the quick tour. Each piece also has a deep-dive of its own (how it's built and what every part does) in the Primitives section.
#Data: schemas and content records
Your data has a shape: a "product" has a name, a price, a photo. That shape is a schema. Each real thing (this product, that post) is a content record that follows it.
The schema does two jobs at once, and this is what makes Tessryx feel like a CMS: it validates your data and generates the form you edit it in. A schema with a name, a price, and a photo gives you an editor with a text box, a number field, and an image uploader, automatically. The admin panel is the schema, seen from the other side.
You edit records in Content Studio; see Content and editors.
#Logic and delivery: workflows and endpoints
A workflow is the recipe that turns your content into a finished thing: a web page, an image, a data response. It's the logic layer, mostly your agent's domain.
An endpoint is a live public URL bound to a workflow. Visit it, the workflow runs, the result is served. Endpoints cover both halves of a site:
- Pages: the HTML a visitor sees.
- API routes: the addresses a page's own buttons and forms call to do things (submit, load more, take a payment).
Endpoints also hold caching: how long a result is reused before it's recomputed. That's the biggest lever on speed and cost; see Credits and caching.
#Automation: schedules
A schedule runs a workflow on a clock instead of on a visit: nightly, hourly, Mondays at 9am. It keeps data fresh with no one touching it: pull a feed each morning, rebuild a summary, send a weekly digest. You switch it on or off; it runs itself.
#Integrations: outside systems and secrets
To reach another service (payments, a CRM, an email sender), your agent builds an integration: a configured call to that system. When it needs a credential, it references a secret.
Secrets are your part. You set a secret's value in the web app; your agent refers to it by name and never sees the value. See Integrations and secrets.
#Media
Images and files your pages use: logos, photos, downloads. Upload and manage them in the Media area; your agent can also generate them. Served fast, with no bandwidth charge.
#Grouping: apps
An app ties a project's pieces into one thing you manage as a unit: a storefront, a blog, a site. See Apps.
#Your address: domains
Sites live at a yourname.tessryx.app subdomain by default. On a paid plan, a custom
domain serves it from your own address, and only then is it indexed by search engines and
free of the Tessryx badge. See Custom domains.
Put together, a site is: content records shaped by a schema (which is also your editor), rendered by a workflow, served at a cached endpoint, kept fresh by a schedule, reaching outside via an integration, grouped as an app, on your domain.