STRUCTURED CONTENT FOR YOUR WEBSITE

Structured content you edit once and show on every page.

Datasets are typed collections for the content that repeats on a website: team members, locations, job openings, menu items. Define the fields, add records in the console or import a CSV, and bind them to any component that repeats, on any site you choose.

The Datasets schema editor in the Aglyn console: a Job openings model with six fields in display order, shared with all sites, listing each field's display name, reference id, type, validation rule and whether it is required

A dataset is not a spreadsheet bolted onto a page. It is a typed model — every field carries a type and its rules, and the console and the API validate each record against it.

WHAT A DATASET GIVES YOU

Model it once. Use it everywhere.

Typed fields, not free text

Text, boolean, integer, number, date and time, coordinates, list and reference — each with its own rules, checked on every console and API write.

Rename the label, keep the id

A field’s display name can change whenever you like; the reference id that bindings, forms and imports use never moves. Descriptions show as hints.

Shared with the sites you pick

Datasets belong to the organization, so a collection can drive pages on any site it is shared with, and the server enforces that sharing.

References and many-to-many

Point a field at another dataset’s records, allow multiple for many-to-many, or create a join collection that pairs two. A delete checks what still points at it.

Forms, workflows and the API

A bound form, a workflow action and the /v1 API write the same rows as the record editor — by id, so renaming a dataset never breaks a binding.

CSV and JSON, both directions

Export streams the whole collection and refuses a short file. Import matches columns by id or display name and validates every row on the way in.

ON THE CANVAS

Bind a component and it repeats.

Point a component at a dataset in the Besigner and it renders once per record. Filter and sort with the same short expressions the console uses, and a repeat badge tells you when a component is data-driven.

Repeat

One component, one record — a list, a grid or a gallery driven by your rows.

Filter & sort

Short expressions like status == Open or posted desc — the same syntax the console’s Data page filters and sorts with.

Limit

Cap each repeat at the rows a section needs — up to 100 records per repeat.

The Datasets records table in the Aglyn console: a Job openings dataset with its datasets, records and storage shown against the plan, above rows of requisitions with code, title, team, headcount, status and posted date

HOW IT WORKS

From a model to a live page.

01

Model

Open the Data page in your organization, name the collection, and give each field the type it needs — with a display name, a description, and the rules it should hold.

02

Fill

Type records in the console, import a CSV or JSON file, point a form at the dataset, or POST them to /v1 on Business and up. The console and the API validate every record.

03

Publish

Bind a component to the dataset and publish. A record you write later shows on the live page within seconds.

ONE PLATFORM

Datasets work with the rest of Aglyn.

Every product below runs on the same platform — explore what else is built in.

Besigner

Design on a live canvas with real components, and publish in one click.

Console

Every site, team, and setting in one place — with roles, billing, and audit built in.

Commerce

Products, carts, checkout, and digital goods — a full storefront on the same stack.

POS

Registers, a kiosk & a customer display.

Forms & Inbox

Build any form on the canvas and collect every submission in one Inbox.

CRM

A form files a lead, a sign-up a subscriber, an order a customer — automatically.

Media

A real DAM — folders, drag-and-drop, and custom metadata for every asset.

Workflows

Automate the busywork — triggers, actions, and logic without leaving the console.

Plugins

Install templates and layouts, or publish and sell your own.

Analytics

Privacy-first traffic, top pages, and store revenue.

Marketing

Email campaigns, announcement bars, popups, and A/B tests — on the site they run on.

Aglyn AI

Describe it, get a draft, edit anything.

Read the Datasets docs →

Included from Starter

Datasets are included from Starter.

Every paid plan carries datasets, records and dataset storage, and the bands rise with the plan. From Starter to Agency, extra datasets are an add-on and storage past your band meters at the published rate.

8

built-in field types

2

ways to share a dataset

2

formats, in and out

7

filter operators

BEFORE YOU START

Questions about the structured content for your website.

Straight answers on what is included, what is gated by plan, and how Aglyn AI helps.

What is a dataset?

A typed collection of records, like team members or locations, that you edit in the console and show on any page that repeats a component.

Can I import a spreadsheet?

Yes. Import CSV or JSON and match the columns to your fields.

Can one dataset power several websites?

Yes. A dataset belongs to your organization and is shared with the sites you choose.

How do I show records on a page?

Drop a repeating component onto the canvas and bind it to the dataset; every record renders as one item.

Which plan includes datasets?

Datasets are available on paid plans, with the number of datasets growing by plan and extra capacity metered.

Is this a CMS?

It is the structured half of one: collections with typed fields, validation and sharing across sites, edited in the same console as your pages.

What is Aglyn?

Aglyn is a website builder with the store, forms, CRM, email, analytics and Aglyn AI built in. It is open source and free to start.

Give your content a model.

Datasets are included from the Starter plan.