BWA goes far beyond a CMS. It is a full enterprise web infrastructure platform that ships CMS, PIM, LMS, member portals, and headless APIs as first-party modules in a single runtime with 88+ production-ready plugins on top. A CMS manages content. BWA manages the entire web application stack, from content to commerce to learning to authenticated portals, all from one admin, one codebase, and one vendor contract.

BWA supports three rendering modes simultaneously: SSR via ASCX modules for fast, SEO-optimised delivery, React with Tailwind via BWA Web Studio for modern component-driven builds and full headless delivery via WebAPI 5.3 REST endpoints consumable by any external frontend, Next.js, Vue, mobile apps, or AI agents. All three modes operate against the same content repository and can be mixed on a single page.

It depends on the project model and no frontend bundler is needed either way. Web Site projects need no build: IIS compiles App_Code and CodeFile modules on first request via Roslyn, so plugins deploy by copying a folder into BWA.Plugins and can be hot-swapped in production without a rebuild or restart. Web Application projects do use a build: their .csproj compiles plugin C# into a single application assembly with MSBuild, so changes to that code ship with a normal build step. Neither model needs webpack or Vite, BWA Web Studio handles the React and Tailwind conversion pipeline separately, producing output that deploys the same way.

Yes. Multi-tenancy is enforced at the data architecture level. Every business object is scoped to a domain ID. A single BWA installation serves multiple independent client websites simultaneously with complete content, user, configuration, and module isolation. New domains are provisioned through configuration, not code changes. Cost is amortised across tenants on a shared AKS cluster.

Advantage Cloud Hosting runs on Microsoft Azure, with SSL, auto-scaling and a 99.9% uptime target. It is included with every plan.

Every plan includes core web content management, dedicated support with free upgrades, key integrations such as Google Analytics and MailChimp with API access, and Advantage Cloud Hosting. Plans are Starter, Professional and Enterprise.

BWA offers enterprise-grade security with SOC2 compliance, runs on Microsoft Azure, and routes every integration through a common authentication layer with an audit trail on a proven .NET foundation.

Three things. Advantage Cloud Hosting runs on Azure with SSL, auto-scaling and a 99.9% uptime target. The security posture is SOC2 compliant, built on .NET and powered by Azure. And single sign-on can be wired through Azure Identity Management alongside SAML and Active Directory.

Yes. Editors work in a visual page builder with the modules already installed on your site, so routine content and layout changes do not become a ticket, a queue and a release window. Developers keep full API access to the same content.

No, and this is the trade-off BWA is built to avoid. Going fully decoupled on most platforms costs editors the visual tools they rely on daily. BWA serves the same content core to a server-rendered site, an API-first front end, or a near-zero-hydration page, editors keep the visual builder either way.

CMS, PIM, LMS and Portal run as independent modules against the same content repository. You add capability without adding another vendor, another login and another integration, which is where fragmentation normally creates business and technical risk.

Every piece of content is scoped to a domain at the data layer, not by convention or by folder. One installation can run many independent sites with full isolation between them.

No. PIM is a native module included in the BWA platform, not a separate product with its own license or implementation project.

It depends on the complexity of your product catalogue and how many channels you're connecting. A discovery call is the fastest way to get a realistic estimate for your specific scope.

No. BWA connects to commerce platforms like Shopify through native connectors rather than replacing them, so your existing storefront investment stays in place.

Yes. Every record is scoped to a domain, so multi-tenant deployments keep product data, users, and configuration fully isolated between sites.

It is a native module, not a bolted-on integration. Courses, learners and progress share the same data hub, the same admin pattern and the same identity system as your CMS, PIM and Portal.

Multiple choice, true/false, short answer and fill-in-the-blank. Assessments can be timed, and auto-grading returns feedback to the learner without an instructor in the loop.

Yes. Certificate issuance is automated on completion, and learner progress is tracked in real time alongside the rest of your platform data.

Yes. Role-based permissions set distinct access for instructors, learners and administrators, using the same identity and permission system as the rest of the platform.

Yes. The LMS integrates with existing systems including HR platforms, CRM and other enterprise applications, so learning activity lives in the same centralized hub as the rest of your operations.

Yes. Video, audio and PDFs drop directly into lessons through the Plyr Media and Audio Player modules, using the same page-building workflow as the rest of the site.

Yes. The same native agentic AI supports intelligent workflows and adaptive learning. AI Block Expressions build course layouts and interactive sections, and AI Assist refines lesson content.

No. Portals share the same identity system as your CMS, LMS, and any other BWA module, so users and admins manage one account, not several.

BWA can support customer, member, employee, partner, dealer, supplier, learning, and public service portals. It can also be extended for specialized industry workflows.

Yes. BWA can be used to modernize the frontend experience, content, documents, workflows, integrations, and access model of an existing portal. The migration approach depends on the current platform and business requirements.

Users can be assigned roles and permissions that control access to pages, content, documents, tools, and services. The access model can be configured around the needs of the organization.

Email and password, magic link, SSO, OAuth, and TOTP two-factor authentication, configurable per site.

Yes. Single sign-on and identity management integrate with Azure Identity Management, SAML and Active Directory, so portal access can run off the directory you already operate rather than a second set of credentials.

Blazor, Bootstrap, React, Vue, Angular and others. The content repository is not tied to a rendering layer, so the framework choice is yours and can change later without re-platforming.

It is a configuration change rather than a migration project. The same content repository already serves your website, your app and any partner or AI system that consumes the API all from one platform you operate.

Yes. BWA exposes documented RESTful services with auto-discovered endpoints, plus webhook support for anything not covered by a native connector.

No. Headless is a delivery mode, not a separate product or a separate installation. The same content core can serve server-rendered pages today and an API-driven front end later, without moving content between systems.

Yes, that is the point of one repository behind many front ends. The same content that serves your website and your app is available to any partner or AI system that consumes the API, over a self-documenting REST surface.

Yes. BWA runs a Model Context Protocol server, so an MCP client can ask the site questions about its content and where you allow it, make governed changes to records. The endpoint is authenticated, and any writes run under the domain's Agent Action policy rather than having free rein.

NLWeb is Microsoft's open protocol for making a site readable by AI agents. BWA implements its /ask endpoint: an agent sends a plain-English question and gets back Schema.org-typed JSON rather than a page of HTML it has to scrape. Every NLWeb instance is also an MCP server, so the two share the same underlying data.

It is anonymous by design, that is what makes a site agent-readable and the safety comes from what it is allowed to see rather than from who is asking. It answers only from content the domain has explicitly published: entities registered as public-read in that domain's API profile, plus published pages. Nothing outside that set is reachable through it.

Yes, it is designed to sit alongside your existing ERP, CRM, DMS and operations stack rather than replace them. Every connector runs through the same authentication layer and audit trail, and anything without a native connector can be reached through the documented REST Web API or webhooks.

The CRM, ERP, commerce and communication tools your teams already use. Integrations are native to the platform rather than bolted on afterwards, so there is no middleware layer, no third-party integration packages and no extra vendor to manage.

You build against a documented contract rather than a black box. There is a documented REST Web API with auto-discovered endpoints, plus webhook support for anything not covered natively.

Every connector runs through the same authentication layer and the same audit trail, on a .NET foundation. Because the connectors are first-party rather than third-party packages, there is no separate patching surface to track per integration.

Yes. There is direct access to the ingestion and transformation layers, you can register custom processors, tap change-data-capture streams, and push structured output to external data warehouses or downstream analytics systems.

Because the connectors are native, new integrations ship in weeks rather than going through a separate procurement cycle for every system, one vendor relationship instead of six.

Yes, through outbound webhooks. Out of the box that includes content being published, form submissions, user registrations, orders and newsletter sign-ups, and any registered entity additionally raises its own created and updated events, so you can subscribe to the records that matter to you rather than polling for changes.

Every delivery is signed. The payload is HMAC-SHA256 signed with your subscription's own secret and sent in an X-Webhook-Signature header, so your endpoint can verify the request before acting on it.

Delivery is retried automatically, the attempt count is configurable per subscription, defaulting to five and every attempt is written to a delivery log, so a failed delivery is visible and diagnosable rather than silently lost.

Yes. You can draw circular geofences around places worth targeting: a campus, a service station, an event lot, a competitor's forecourt, and tie a campaign to them. The campaign carries the offer; the fence only decides where a visitor has to be for it to apply. Fence types are an editable list, so you can group them however your team thinks.

No, and that is deliberate. Fence coordinates never reach the browser, the visitor's position is posted to the server and the containment test runs there. Sending fences to the client would publish the list of locations you target, competitors' included, to anyone who opened the network tab.

The BWA Bot Accelerator Framework is a production-ready framework built entirely on Microsoft Azure AI services, OpenAI, AI Search, CLU, and Cognitive Services. Stan, the first bot deployed on the framework, went from kickoff to production in 8 weeks. Starter engagements typically run 4 to 6 weeks.

It is native to the platform, not a separate purchase or a bolted-on integration. Agentic AI is built in and works against the same content and permissions as everything else.

Two things today. AI Block Expressions generate page layouts and interactive sections, and AI Assist refines existing content in place. Both run inside the normal authoring workflow rather than in a separate tool.

Stan is BWA's conversational platform assistant. You ask it questions about the platform in plain language and it answers from a maintained knowledge base, citing what it drew on rather than answering from memory.

Stan covers BWA platform questions. Account, billing and unrelated topics are out of scope, it will point you to your support contact rather than attempt an answer. Where a question is ambiguous it asks one clarifying question instead of guessing, and where it has no grounded answer it says so rather than inventing one.

Typical questions are the practical ones that come up while building: how to create a new content module, what the difference is between CMS and Headless mode, how plugins work, how to add a shortcode to a page, where the AI Block tool is, and what the LMS quiz container does.

Built in and ready to use: AI Block Expressions for generating layouts and interactive sections, AI Assist for refining content in place, agentic workflows across the modules, and Stan for platform questions. Built by you: a customer-facing assistant of your own, using the BWA Bot Accelerator Framework on Microsoft Azure AI services.

Through a per-domain Agent Action policy, and the defaults are deliberately cautious: agent actions are off until enabled, and dry-run until you turn that off. Beyond that you allowlist which verbs are permitted, create, update, publish, configure, revert  and which entity types they apply to, cap how many actions can run per hour, and read a full audit log of everything attempted, with a configurable retention period.

No. Generated blocks are placed as managed markers rather than pasted-in markup, and the engine resolves each marker to whichever version is currently live when the page renders. That means a block can be promoted, reverted or archived without anyone re-editing the page it sits on.

It works in treatments rather than rewrites, recolour, animation and layout which stack at render time. Each kind is promoted independently, so applying a new animation does not discard the recolour you already approved, and any treatment can be reverted on its own.

Yes. A site-wide Generative Engine Optimization policy sets which AI crawlers may read the site, held as explicit allow and deny lists rather than a single on/off switch, so you can admit the engines you want to be discoverable in and exclude the rest.

BWA builds /llms.txt for you, a Markdown index telling an AI agent what your site is and which pages answer what, so it does not have to parse your HTML chrome to work it out. Worth being straight about it: llms.txt is a proposed convention, not a ratified standard, and no engine is obliged to read it. It costs little and helps where it is honoured.

Functionality ships as self-contained plugins from a curated library covering workflow automation, data and analytics, third-party integrations, security and access control, and content management. Each one is documented, compatibility-checked, and installs by copying a folder and registering the module.

Copy the folder, register the module, deploy. Every module follows the same conventions, the AdvantageModule base class, fetch() rather than postbacks, a bwa- CSS prefix, WebAPI controllers and a complete admin dialog, so it behaves like everything else in the admin once installed.

They are a curated, verified catalogue rather than a community marketplace. There are 88 modules organised by business need: workflow automation, data and analytics, third-party integrations, security and access control, and content management - each with compatibility checks, full documentation and expert support.

Yes. Designers work in Figma, and BWA Web Studio converts React and Tailwind designs into production ready BWA modules using Babel AST parsing with a zero-regex policy, so the conversion understands the code structure rather than pattern matching it.

No, design to production runs as one pipeline. Web Studio takes the design through to deployable modules, which then behave like any other module in the page builder, so the handoff from design to build is not a rewrite.

A whole multi-page design project imported in one go rather than a page at a time. A dealer site might be twenty-five pages; a pack brings all of them in together, gives you a page menu, and lets you set the brand and the business's own details once for the entire pack. Each page then goes through the same conversion pipeline as a single-page import.

No. The automotive pack is the blueprint, but the loader itself is sector-agnostic. Another vertical is authored the same way, design the pages, then ship a pack manifest declaring the sector, the sample identity strings the pages contain, and each page's slug, title and entry point.

Settings are split deliberately. Pack-wide covers brand, archetype, design system, chrome, corner language and the business's own details: name, tagline, phone, address and an uploaded logo. Change any of those on one page and every other page follows. Per-page covers only each band's treatment, whether it is shown, and the band order.

Yes, when the design has one. Each page is rendered twice, once at desktop width and once at phone width, so the design is driven into its own mobile state rather than just being narrowed. A design authored only at desktop width still converts, but what you get is a squeezed desktop composition, so author the mobile state if mobile matters.

The design brief is generated from the installed module catalogue rather than written by hand, so a design cannot name a module that does not exist. An upload gate then validates the pack before any conversion is spent on it. One limit worth knowing: WebStudio can confirm a module exists and is installable, but not that it is registered on a particular customer domain that lives in the tenant database and should be checked on the target domain.

Three sources, all converging on the same conversion pipeline: a Figma frame, a Claude Design or HTML project, and a multi-page Design Sector Pack. Whichever you start from, the conversion passes through a human approval step before anything is generated.

Real modules wherever it can. Web Studio reads the names in the design, section names, and above all the field names inside repeating items to bind each band to an existing module by reference. Where no module matches, the band falls back to an AI Block: it installs and works, but it does not yield a reusable module, so naming things in line with the platform's conventions is what keeps a design importing as modules rather than as blocks to rework later.

Through a Brand Corpus, a versioned snapshot of your brand's palette, typography, design tokens and approved layout patterns for the tenant. Generated content is produced against those tokens rather than against whatever the model felt like, so output inherits your brand instead of approximating it.

Yes. The Brand Corpus has a staged / live / archived lifecycle with revert, so a brand update is an auditable, reversible resource rather than an edit you cannot undo. Exactly one corpus is live at a time, and the previous one stays available to revert to.

Anywhere HTML is rendered. The shortcode engine runs as a response filter over outgoing HTML, so a token works in page modules, in editor content, and in snippets or code blocks saved from the rich-text editor, not only in places a developer wired up in advance.