TECFINITY
The Framework
Aviant Engine.
The multi-tenant content management system we operate ourselves. One installation runs many client businesses: each gets its own projects, languages, domains and access keys, and a website that reads from it.
The Aviant Advantage
Aviant is not software we hand over and leave. We run it — which is why it is built around keeping each client's content strictly separate, and around setting a new client up without slips, rather than around a marketplace of add-ons.
Separate by Construction
Every piece of content carries the client it belongs to, and nothing is read or written without that check — there is no default to fall back on. A system that forgot whose site it was serving would show one client's content on another client's website.
Modules per Project
Blog, commerce, forms, portfolio, marketing, SEO and sector-specific modules are switched on per project and enforced wherever content is requested, so a client's installation contains what they bought and nothing else.
Provisioning in One Transaction
Setting up a new client — their account, login, subscription, project, languages, domain and access keys — happens in one step that either completes or does nothing at all. It replaced six disconnected screens and the mistakes that lived between them.
Publish Once, Anywhere
Content is published through one documented service, with keys that are tied to a single client, locked to their own website and revocable at any time. The websites that read it are separate builds — which is exactly how the client sites in this showroom work.
Content-level Localisation
Languages are treated as content in their own right rather than as translations of one another, so the Greek and English sides of a site can genuinely differ — and search engines are only ever told a page exists in another language when it really does.
Open Core, Closed Engine.
As a Social Cooperative Enterprise, we believe in giving back to the developer community. While the Aviant Engine remains proprietary, we maintain the foundational Aviant Core Library as open source.
View Aviant Core on GitHubOne Core. Any Application.
The same engine backs a marketing site, a news archive and a fight promotion's roster — the difference is which modules are on.
Sites
Client Websites
Pages with version history and scheduling, reusable blocks, menus and forms, edited by the client and read by a separate front end over the API.
Commerce
Editorial & Commerce
A blog module with authors, series, categories and editorial workflow, and a commerce module covering products, orders, inventory, discounts and shipping.
Verticals
Vertical Modules
Purpose-built domains for a sector — the combat-sports module supplying fighters, events and promotions to a client's public site — off by default for everyone else.