Skip to main content

What's New

The features Aglyn shipped most recently, grouped by area. Each links into its section for the how-to.

September 2026 — screens are now pages (newest)​

  • Screens are now called pages — everywhere Aglyn names them: the Pages tab in the console, the Besigner, emails and notifications, Aglyn AI and these docs. Only the name changed. Nothing about your site does: its addresses, its content, how it publishes and your plan's limits stay exactly as they were, and the console's own links and the screens data a plugin reads keep their names, so nothing you built needs changing.

September 2026 — Aglyn AI​

  • Aglyn AI — the assistant builds as well as answers. Describe what you want and it plans the work, builds it from what your site already has, and hands you a draft: a page, a whole small site, a layout, a page template, a reusable component, a form, a section on the canvas, rewritten copy, a theme change, search titles and descriptions, product copy and catalog ideas, help working the CRM, a designed email or campaign, and what your analytics mean.
  • Nothing is published — every generation writes a draft or an unpublished version. It never flips a live page, never registers an address, never touches your navigation and never sends anything. You publish what you want, through the buttons you already use.
  • The building rules — reuse before creating, site-wide regions in the layout, forms built on the Forms page and placed by reference, your theme's colors and spacing rather than fixed values, images from your media library with alt text, one main landmark and headings in order, responsive at your theme's breakpoints, and a measured size for every output. Every plan and every generated document is checked against them before you see it, and an answer that breaks one is re-asked rather than handed over.
  • The plan comes first — a build job proposes what it will reuse, what it will create and why, and the screens it will build, with an estimate in credits. Nothing is generated until you confirm it.
  • The Aglyn AI add-on — bought once for the workspace on any paid plan, it widens your monthly band of AI credits rather than adding a second meter. Starter gains a band it did not have; Free workspaces generate against their monthly allowance and are never billed; Enterprise carries it by agreement.
  • Allotments, usage and model choice — give one member, one site collaborator or one whole site its own monthly share of the pool, hard or soft, so one client site cannot spend what everyone else was counting on. Everyone sees their own usage while they work and can pick which model answers, or leave it on Auto.
  • AI off for one site — a site admin can switch AI off for one site without touching the workspace's add-on, credits or other sites.

Drafting an automation from a description is not part of this release — see Explain automations with AI.

September 2026 — the CRM​

  • The CRM is included from Starter — every part of it, from leads and contacts to companies, deals, tasks, reports, fields and settings, comes with a paid plan, and Free includes none of it. On Free the CRM tab stays in the navigation, with every section shown locked beside the upgrade notice. Capture does not depend on the plan: forms, sign-ups, orders and bookings still update the people your workspace holds, and exporting them or erasing a person on request is under Settings → Privacy on every plan. On a paid plan, records past your band now bill as overage on the monthly invoice.
  • AI assist past the included band — on a paid plan the assistant now keeps answering once your included credits are used, and the extra credits are billed at your plan's per-1,000 rate on the monthly invoice. A switch under Billing → Usage → AI assist overage, Stop AI assist at the included band, stops it there instead; it is off unless you choose it.
  • The CRM hub — what was the Contacts tab is now CRM: one tab, seven sections at …/crm/<section>. Contacts get their own record pages and can be added by hand; leads are worked and converted into a contact, a company and a deal; the deals pipeline is a board with a weighted forecast; tasks, reports and custom fields each have a section. The list gains CSV import, bulk actions and a timeline of logged calls and meetings; every section's table selects, acts and exports as a CSV that re-imports, and companies import too; and automations gain CRM events and steps. Links to the older /contacts address still open the hub.
  • Email templates and snippets — the one-to-one email from a record picks a Template that fills the subject and body, inserts a Snippet at the caret, and saves the letter you just wrote as either. Both take merge fields — {{contact.firstName}}, {{deal.name}}, {{sender.name}} — filled at send time and previewed as you type, with the fields that have no value counted under the message. Shared templates are every editor's; personal ones are yours. Managed under CRM → Settings and over the REST API.
  • Saved views in the CRM — every CRM list keeps its filters, columns and sort under a name: open a view from the views menu or from its link, share it with the team, make it your default for the section. The Contacts list gains a filter bar with owner, stage, source, company, tags, dates, purchases and one filter per custom field; a saved contacts view can be an email audience beside a segment.
  • Companies, pipelines, deals, tasks and activities over the REST API — the CRM's records join contacts on /v1, under one pair of scopes, crm:read and crm:write. Create a company keyed by its domain, open a deal and move it through its pipeline by stage or by status, assign a task with a due date, and log a call as it ends. Every list takes ?updatedAfter= for a sync that walks only what changed. A contact gains its CRM profile — phone, job title, company, owner, lifecycle stage — written per site and readable as one, and /v1/usage reports the size of each collection.
  • Functions that can carry a calculator — an expression can call min, max, round, floor, ceil, abs and format, and can read any site variable by its name, so a price lives in one variable and every page and calculator follows it. A parameter takes a label, a starting value and a list of choices, and the Function Widget asks each one as what it is — a number box, a switch, a list — shows several named results instead of one, and can update as the visitor types. For a design of your own, the Calculator elements bind inputs, results and conditional rows to one function anywhere on the canvas.

August 2026 — the canvas, up close​

  • Style hover, focus and the other states — a row of chips under the breakpoint chip: Default, Hover, Active, Focus and Disabled. Pick one and the whole styles panel switches to that state, with the element held in it on the canvas so you can see what you are doing. Fields you don't touch keep inheriting, states combine with breakpoints, and Focus is :focus-visible — keyboard focus, so styling it can essentially only add an indicator, never remove one.
  • Text is edited on the element itself — double-click and you are typing into the real heading, at its real size and weight, with the page reflowing around you. The selection chrome stands aside while you type. Escape cancels, Enter commits a plain element, and a wrapped line of inline text is now outlined line box by line box instead of by one rectangle covering its neighbors.
  • Formatted text belongs to the canvas — once an element carries bold, links or lists, the panel's Text field shows it read-only and says why, rather than letting a plain edit silently throw the markup away. Remove formatting keeps every word and line break, drops the formatting, and is one undo step.
  • One box styler, on your theme's spacing ladder — margin, border, padding and contents in a single diagram, with the sides named in words rather than as mt / ml, and a value shown on each side once it is set. Space is set from nine named steps that follow your theme, or an exact amount whose unit is explained where you pick it.
  • Rooms are per version — co-editing pairs you with the people on the same version of a document, matching where the live edits actually flow. Two people on different versions no longer see an avatar promising a connection that isn't there.
  • See who's in a document before you open it — avatars on the row in the Screens and Layouts lists and the Components, Templates and Site emails cards.
  • User accounts are a switch per site — visitor sign-in is off until you turn it on, so a brochure site does not quietly serve /signin, /signup and /recover. Turning it on serves them and puts the Members elements in the editor; turning it back off hides the pages and deletes nothing.
  • Report an issue asks the right questions — the dialog says plainly what it is and is not for, then asks per-kind: what you were doing and whether it happens every time for a bug, what you are trying to do that you can't for an idea. A question is checked against the documentation first, and often answered without filing anything.
  • Assist shows its sources — every written answer now lists the documentation sections it drew on, as links you can follow.

August 2026 — knowing what happened​

  • Bandwidth, and what happens past it — every plan's monthly traffic allowance is now enforceable. On a paid plan the extra is metered and billed and your sites keep serving; on Free the site is paused until the start of next month, clears itself when the month turns, and comes straight back if you upgrade. Nothing is ever deleted.
  • Run history that says what happened — the Runs dialog is a real log: when it ran, what triggered it, whether it succeeded, and what each step did. A run stopped by an unmet condition is recorded as Skipped, naming the field — the answer to "why didn't my automation fire?".
  • An Inbox of people, not forms — a submission shows who sent it, how long ago, and where it went: chips under the fields say whether it also became a dataset record.
  • Count your recipients before you send — the campaign composer counts the audience while you are still writing, with duplicates, unsubscribes and your monthly cap already taken off.
  • Popups that cap once per session — show a popup at most once per visit, or hide it for a number of days after it is dismissed. Scheduled campaigns now actually send, every fifteen minutes.
  • Average time on a screen — beside a screen's views, how long visitors stayed. The Traffic card was rebuilt too, and its growth figure now follows the range you picked.
  • Download any asset — from the detail drawer or the card menu, for public and private files alike, and the drawer says which CDN variants that file actually has.
  • The Orders screen you were promised — a real table with a Channel column, colored status pills, and revenue, order-count and average-order-value tiles against the previous 30 days.
  • Free listings say Free — the marketplace shows a price on every card, stars where a listing has been rated, and a What's included box on the listing page.
  • Make the platform yours — white-label now reaches transactional email: your logo in the header, your product name and support URL in the copy. Self-hosters can rename the product itself and serve every site from their own apex.
  • Report an issue — a bug report from any console page, on every plan, with the page, workspace and version attached for you.

August 2026 — editing together​

  • A visual editor for long documents — the Markdown element's Content attribute is a WYSIWYG editor, not a text box: headings, bold, links, lists, quotes, images, code and tables from a toolbar, pasting from a Google Doc keeps its formatting, and a Markdown switch shows the raw source when you want it. Editing a whole policy page no longer means preparing one long paste.
  • Live co-editing — open the same screen, layout, component, template, or designed email as a teammate and edit it together: presence avatars in the toolbar, each collaborator's cursor and selection on the canvas in their own color, and element-level live changes that never disturb your undo history.
  • Concurrent-save protection — if someone else saves the document you're editing, the besigner pauses saving and tells you the moment it happens, keeping everything on your canvas until you reload. No silent overwrites, in either direction.
  • Local draft recovery — the besigner keeps a local draft of unsaved work in your browser; after a crash or an accidental close, it offers the work back with Restore / Discard.
  • Apex custom domains — connect the bare example.com, not just www: an ALIAS/ANAME to sites.aglyn.app (or an A record, where your registrar has no ALIAS) verifies in the same Verify & connect click as a CNAME.
  • Edit from the live site — an admin bar on your published site that jumps from any live page straight into the besigner for the screen serving it.

Besigner copy & paste​

  • Copy and paste elements — copy any element with its children and paste it somewhere else, including into a different screen, layout, component or template. Available from the ⋮ menu on the canvas and in the hierarchy, or with Cmd/Ctrl + C / V. Multi-selections copy in document order, and a paste that would bring in an element the target document doesn't have is refused with a message instead of landing half-finished.
  • Cmd/Ctrl + A now selects every element at the same depth as the current selection.

Scalable audience pricing​

  • Unlimited member accounts on every plan — visitors who sign up to your published site are never metered, capped, or charged per account, on any tier including Free.
  • Contact audience bands — your contacts CRM is priced as an included band per tier. On paid plans, growing past the band never drops a record: extra contacts will bill as small metered overage ($0.25–$1.00 per 1,000/month, cheaper on higher tiers). The billing page has a new Contacts meter with a live estimate. Overage billing began when the CRM opened to every workspace.
  • Clearer seat language — what plan cards used to call "members per host" is now site collaborators: per-site teammate seats. Member accounts were never seats.
  • Platform fees on the plan cards — each tier now shows its declining transaction-fee ladder, including the digital rate that applies to paid memberships and gated content.

Marketplace at the organization level​

  • One Marketplace for the whole organization — browse, install, manage and publish marketplace items from a single Marketplace destination in the organization navigation (Browse, Installed, and Publish tabs), instead of a per-site Marketplace tab. Old per-site links redirect here.
  • Marketplace is the market; Plugins is the switchboard — the two live side by side in the organization navigation and do different jobs. Marketplace is where you browse, install and publish. Plugins is where you turn things on and off: an Installed from the marketplace card and a Built in card, each row with a switch and its per-plugin settings. Look for a plugin's on/off switch under Plugins, not under Marketplace. The seller area is its own set of marketplace sections — Publish, Publisher Profile, Listings, Payouts and Sales. Old per-site links redirect into the matching organization section.
  • Install targeting — when you install, choose All sites (organization-wide, and any sites you add later) or Selected sites. Site-scoped artifacts (components, templates, layouts) install onto every current site and note that new sites aren't added automatically.
  • Publish from any site — the Publish tab picks a source site, then a component, a layout, or the whole site as a template. The per-site Publish shortcuts still work.
  • Dataset schemas and email templates are publishable — share the field model of a dataset (structure only — records never travel) or a transactional email you've designed. A schema installs as a new empty dataset with its reference fields relinked by name; an email installs as a draft version, so it never replaces an email a site is already sending.

REST API & API keys​

  • The Aglyn REST API — programmatic access to your organization's datasets and records (full CRUD), contacts, sites, and form submissions, authenticated with API keys you create under Organization → Settings → API keys. Keys are scoped, shown once, and Business-tier; the API supports cursor pagination, per-key rate limits, idempotent writes, and a consistent error envelope. See the new API reference.
  • Record a shipment over the API — the new Orders — record shipments key permission lets a 3PL, a warehouse system or a label printer mark an order fulfilled or delivered and attach the carrier and tracking number, so a store can be both sold from and shipped from outside the console. It obeys the same order-status rules the console does, and sending the same request twice records the parcel once.

In-console help​

  • Documentation from the console — the account menu now has a Documentation entry that opens this site in a new tab, and feature pages grew a small ? icon next to their titles: hover for a one-line summary, click through for the full docs page.
  • Help everywhere — the same ? affordance now covers cards, form fields, table headers, the staff console, and the Besigner's style and attribute panels, each deep-linking to the exact docs section it explains.
  • Dropdown Panel preset — a primitive-built hover panel (Stack + Button + hidden panel) that inserts with its hover choreography pre-wired as editable interactions: show on hover with Esc/outside-click dismissal, hide on leave with a 250ms grace delay. Show/hide steps themselves gained Delay and Close on Esc / outside click options in the interaction builder.
  • Menus & navigation — a Dropdown Menu, a Mega Menu with a free-form wide panel, a slide-in Drawer with a Menu Button, and a one-insert Mobile Nav preset. Every menu click-toggles out of the box; hover opening (and anything fancier) is authored as an interaction. Interactions gained hover enter/leave triggers, a repeatable every time frequency, element show/hide actions with a canvas element picker, and menu and drawer open/close actions; the styles panel gained a per-device-band Visibility control.

Designed content collections​

  • First-class blog pages — collection list and entry routes render through your site theme and shared layout. Pick a List template screen and an Entry template screen per collection in Content, drop the new Collection Entries block (repeats title, date, excerpt, Read more per published entry — works on any screen via its collection-slug attribute), and render markdown with the themed Entry Body block. With no template set, the built-in pages still compose inside your theme and default layout.

Self-serve add-ons​

  • Add-ons — buy manager and member seats, extra datasets, extra sites, POS registers, and the Event Calendar straight from Billing → Add-ons: prorated previews before every change, hard caps where your plan tops out, and quantities that re-price automatically on plan switches. No more asking support to enable an add-on.

Designer & email wave​

  • Responsive styling — the artboard preview mode now scopes style edits per breakpoint (XS–XL), the box stylers are fully interactive with side/axis/all fan-out and units, and every element takes custom classes plus a CSS builder (builder / raw CSS / raw JSS) on its sx.
  • Designed emails — build campaign emails in the besigner with email-safe blocks and merge tokens; campaigns pick templates by id and support test sends.
  • Rename-safe references everywhere — products, collections, categories, datasets, and screens are picked from lists and stored by id; the reference-health audit flags anything dangling.
  • Console reorganization — site users and analytics get their own sections, the dashboard gains commerce and campaign glance widgets, and the Products/Marketing/Workflows hubs are tabbed with ?tab= deep links. Notifications + Manage Account live under a personal Manage area.
  • Redirects v2 — prefix and regex match modes with capture substitution ($1), priority ordering, and an inline tester.
  • Org & team v2 — organization logo + contact details, a team member detail page with role/title editing and per-member activity, personal marketplace profiles, and profile images for every user.
  • Staff console v3 — impersonate a user or an org's owner (audited, bannered), edit orgs and user identities directly, and paginated, card-styled admin lists.

Ecommerce platform​

The biggest wave yet turns every Aglyn site into a full store, competitive with Shopify and Squarespace:

  • Product catalog — variants and options, categories, tags, smart collections, Shopify-compatible CSV import.
  • Storefront blocks — product grids with facets, product pages with variant pickers, cart drawer + checkout with wallets, customer accounts, wishlists, newsletter capture. All designable in the besigner.
  • Digital goods — secure downloads with automatic update re-delivery, license keys, subscription products, members-only content and video.
  • POS & reservations — a console register (cash, QR card, room folios) and date-range stays with deposits.
  • Growth tools — discounts engine, gift cards, abandoned-cart recovery, verified reviews, related products, back-in-stock alerts, and a commerce analytics dashboard.
  • New pricing — Starter $16, Pro $39, Business $99, and the new Advanced $299 (annual), with platform fees that drop to 0% as you upgrade. Pricing and the features included in each tier are provisional during pre-release and may change at any time.

Latest polish wave​

The newest round tightened every marketing, billing, and operations loop:

  • Overlays now track per-overlay views, clicks, and dismissals — mirrored into your GA property as aglyn_overlay events.
  • Campaigns gained {{firstName|there}}-style merge tags and scheduled sends with cancelation.
  • Experiments can end on a date or auto-declare a winner at your chosen confidence level, and exposures/conversions mirror into GA as aglyn_experiment events.
  • Automations picked up frequency controls: once per session, once per visitor, or a cooldown window.
  • Workflows log every run with outcome and duration; the Logic page's Reference health card flags automations pointing at deleted workflows, datasets, or functions.
  • Dataset imports can upsert on a key field instead of appending duplicates.
  • Billing added the Stripe Billing Portal for payment methods, a past-due banner during retry windows, and usage-threshold notifications to org admins.
  • The Marketing hub opens with an at-a-glance rollup of live overlays, email engagement, and experiment states; commerce orders now notify site managers in-app.

Build & design​

  • The Besigner — multi-select across hierarchy and canvas, whole-selection multi-drag, reliable reparenting with placement markers, inline and basic rich-text editing, and clearer "why this drop was rejected" messaging.
  • Screens & layouts — hierarchical routing with cascading slug rewrites, shared layouts with slots, reusable components, and named versions with scheduled publishing.
  • Theme builder — site theme editor with live preview and light/dark schemes, supplied to the canvas so previews match the live site.
  • Templates, blocks & content — starter template gallery, save-site-as-template, a section & block library, and a blog with collections and RSS.

Data​

  • Datasets & dynamic content — typed model builder, typed document editor, relations (including many-to-many), a query layer, repeatable components, and CSV/JSON round-tripping.
  • Bindings, variables & functions — rename-safe id tokens, a picker-first insert experience, a no-code function builder, and a where-used safety scan.
  • Site search — search across pages and dataset records.

Media​

  • Media library & CDN — folders as grid cards with drag-and-drop organizing, one shared picker everywhere, metadata (including your own custom key/value pairs) and bulk edit, image transforms, replace-in-place, an on-demand Used on audit, large video uploads, and CDN delivery with WebP variants (paid). Media URLs are stable: replacing a file or moving it between folders never breaks an existing embed or a link you already copied.

Grow​

  • Forms & lead capture — form components, an inbox reader, and dataset-backed submissions.
  • CRM — unified ingestion from forms, members, orders, and bookings, with tags, notes, CSV export, segments and a REST API.
  • Email campaigns — audiences, tiered send caps, and unsubscribe handling.
  • Marketing overlays — a site-wide announcement bar and promotional popups v2 with triggers, capping, scheduling, email capture, and metrics.

Sell​

  • Commerce — starter selling plus commerce v2 (receipts, inventory, coupon codes) and an orders page with filters and CSV export.
  • Bookings & scheduling — services, availability, a booking widget, Stripe payments with slot holds, and reminder emails.

Reach & measure​

  • SEO toolkit — per-screen SEO, sitemap/robots, JSON-LD, and Open Graph/Twitter cards.
  • Analytics — pageview beacon, insights (referrers, devices, ranges), and per-screen traffic (Pro+).
  • Multilingual — locale variants, hreflang, and a language switcher (v1).

Extend & automate​

  • Plugins & marketplace — a plugin registry with install/upgrade, a sandboxed runtime, per-plugin config, a network bridge, and marketplace monetization.
  • Workflows, actions & webhooks — event-to-action automation, workflows on site events, and outbound/inbound webhooks.
  • AI assist — copy assist for any text prop and AI Generate Section.

Operate​

  • Teams, roles & membership — custom roles with per-member overrides, and members-only site areas.
  • Billing & plans — aligned tiers, entitlement gates, usage meters for every quota, and seat add-ons.
  • Custom domains and redirects — self-service domain setup with DNS verification, and a redirect manager with loop checks and hit metrics.
  • Site protection & error pages — per-screen passwords, custom 404/401/403/503 screens, and maintenance mode.
  • Staff console (Aglyn staff only) — tenant management, entitlement editor, users admin, suspension, and an audit viewer.
  • Feature flags (Aglyn staff only) — Remote Config–backed release gating with percentage rollout; staff preview unreleased features with warnings.
  • Organization workspaces — orgs own multiple sites with shared billing, role-based membership with per-site access, and Slack-style workspace subdomains (architecture).