Start With the Dashboard. Expand When You Deploy.

Every governance conversation seems to start with a migration

Web teams that want control over a sprawling estate are often told the answer is consolidation: move everything onto one CMS, one host, one theme. That is often a multi-year project that needs budget few teams have, and it can stall while the sprawl keeps growing.

There is a smaller first step. See everything first. Decide what to change after.

What dashboard-first means

Accorbis is a standalone web governance platform. It gives one dashboard across the WordPress, Drupal, and custom sites an organization already runs. It is not a CMS and not a hosting company.

Starting with the dashboard means you subscribe to the platform, run discovery, and govern the sites where they already live. Nothing moves. Accessibility, performance, uptime, and security scores show up across the estate. Owners, policies, and alerts come from one workspace.

Most estates should start here, and they can stay here. Dashboard-only is a real product, not a trial.

Expand only when you mean to

Starter kits, included

When a department needs a new site, Accorbis starter kits deploy a starter site the team then makes its own. They come with the platform subscription. A starter kit is a starting point, not a finished flagship site.

Hosting, a separate decision

Hosting isn’t included with a starter kit. It is a separate line, only for sites you choose to host with Accorbis, and it is never assumed.

Custom organization kits and implementation

Kits built to your organization’s brand and standards need real setup work. So does migrating or rebuilding sites. Those are services from your implementation partner, scoped separately from the platform.

Why this order works

• Faster value. You see the estate without waiting for a migration.
• Better decisions. You choose what to retire, fix, or rebuild from data, not guesses.
• No forced moves. Sites stay on WordPress, Drupal, or custom stacks as long as that is the right call.

When dashboard-first is not enough

If most of your sites are on unsupported platforms, or the estate is being rebuilt anyway, you may move faster into new sites and hosting. Even then, the inventory comes first, so the rebuild covers every site that should exist.

A hypothetical: two ways to start

Imagine a university that decides it needs governance. One path starts with a CMS consolidation project. It needs a long budget request, a platform decision, and a migration plan before anyone sees the full estate. The other path starts with the dashboard. Discovery runs, every site appears with its scores and owner, and the consolidation decision is made later with real data, or turns out to be unnecessary for most sites.

Both paths can end in the same place. Only one gives the team a full view first.

What the first months on the dashboard look like

1. Discovery: every site on your domains appears in one view.
2. Ownership: each site gets a named owner, or is flagged.
3. Scores: accessibility, performance, uptime, and security across the estate.
4. Policy: rules and alerts that apply to every site.
5. Decisions: retire, merge, fix, or keep, based on what you now see.

Decision criteria for expanding

• Use starter kits when departments ask for new sites and you want them governed from launch.
• Consider hosting only for sites where moving the hosting is the right call on its own merits.
• Scope custom organization kits when your brand and standards need a starting site built specifically for your organization.
• Bring in implementation when the work the dashboard reveals outgrows your team.

Common objections, answered

“We will just have another tool to manage.”

The dashboard replaces spreadsheets, scattered scan reports, and guesswork. It puts the estate you already manage in one view.

“We need to consolidate first.”

Consolidation is easier to plan when you can see every site, its platform, and its condition. Starting with the dashboard does not rule it out.

“Our sites are on too many platforms.”

That is the situation the dashboard is built for. WordPress, Drupal, and custom sites appear side by side.

Key terms, defined

• Dashboard: the Accorbis platform subscription, one organization-wide view of every site with inventory, scores, policy, and alerts.
• Starter kit: included with the platform; it deploys a starter site your team makes its own.
• Custom organization kit: a starting site built to your brand and standards; it needs setup and is not included.
• Hosting: a separate line, only for sites you choose to host on Accorbis.
• Implementation: services from your implementation partner, such as setup, migration, and remediation.

Frequently asked questions

Do we have to use Accorbis hosting?

No. Dashboard-only governs the sites you already host wherever they are.

Are starter kits included?

Yes. Starter kits come with the platform. Custom organization kits that need setup are not included.

Does Accorbis replace our CMS?

No. WordPress, Drupal, and custom sites stay. Accorbis sits above them.

Is implementation part of the subscription?

No. Implementation, migration, and custom kits are services from your implementation partner.

Can we stay on the dashboard indefinitely?

Yes. Dashboard-only is a complete way to use Accorbis.

How do we start?

With a 30-minute working session against your estate. No slide deck.

What do we need to prepare for the first session?

A list of the domains you own and the questions you most want answered about your estate.

Is hosting required to use starter kits?

Hosting isn’t included with a starter kit. Ask in your working session how a starter site would be deployed and hosted for your estate.

Start here

Schedule a 30-minute working session against your own estate.