Custom Domain Sites

Publish findings under your own domain.

Give approved readouts a home that matches your organization’s identity.

  • Give published readouts a branded home under your own domain
  • Create an outward-facing destination without turning every Project into a public website program
  • Keep access and publication rules clear as the audience grows
Run the orientation Talk about branded sites Explore pricing & plans

How pricing works

Add a custom domain to Publishing when approved findings need a branded external destination.

  • Typically scoped as an organization-facing publishing layer.
  • Best when a branded domain and outward-facing presentation matter.
  • Not necessary for internal-only reporting or early-stage bounded Projects.

Why teams add Custom Domain Sites

Give reporting a credible public home

Custom Domain Sites let organizations publish under their own identity instead of sending people to an anonymous project endpoint.

  • Support branded trust-building destinations
  • Create cleaner public or partner-facing access points
  • Help publication feel intentional rather than incidental

Separate collection from presentation

The collection layer and the sharing layer serve different jobs. A custom site keeps that distinction visible.

  • Collect first, publish later when the work is ready
  • Use a branded site only when the audience actually needs it
  • Reduce pressure to overbuild every Project from day one

Keep communications and access consistent

For public, civic, or institutional work, where something is published matters almost as much as what is published.

  • Strengthen legitimacy with a recognizable destination
  • Create a better fit for public-facing or panel-gated outputs
  • Make the publication layer feel like part of the organization, not a bolt-on tool

Where it fits best

Public service and civic teams

Use it when: When the work needs a public-facing or partner-facing reporting destination under an institutional identity.

Value: Improves trust and coherence when results need to travel beyond the project team.

Research and insight groups

Use it when: When sponsor, client, or participant-facing reporting needs a branded home instead of a raw report URL.

Value: Creates a more polished and credible presentation layer.

Transformation and communications teams

Use it when: When sharing is part of change management, transparency, or stakeholder accountability.

Value: Connects the work to a recognizable destination without overextending the collection layer.

What this enables

  • A branded destination for governed publishing
  • A clearer separation between working space and external presentation
  • More confidence when findings need to be shared publicly or selectively

How teams usually bring it in

  1. Confirm that the work really needs a public or partner-facing destination
  2. Set up Publishing first and agree what each audience can see
  3. Layer in the custom domain site once branded external access becomes part of the requirement