FAQ

Who is RealMosaic for?

RealMosaic is primarily for small to mid sized agencies and solo web designers managing multiple client websites. It can also suit marketing teams and niche organisations working with Subtle Difference on a managed website. It is designed for teams that value reusable delivery, controlled client editing and managed platform infrastructure.

What makes RealMosaic different?

RealMosaic combines an agency CMS workflow with managed infrastructure and direct platform support. Agencies can reuse themes, manage multiple client sites, control client editing and work without a separate front end build process for normal site delivery.

Why Units instead of per site pricing?

Units measure capacity across your whole portfolio rather than applying one fixed price to every site. This lets smaller and more demanding sites share the same plan. Higher tiers reduce the cost per Unit as your portfolio grows.

What happens to our client's content if they leave?

Client content belongs to the client. RealMosaic can export site content as structured JSON with the associated assets. Moving to another CMS still requires a planned migration because themes and platform features are specific to RealMosaic.

What is RealMosaic not suited for?

RealMosaic suits business, publishing and content websites that fit its theme, content and module model. It is less suitable for one off builds with no ongoing relationship, projects that require substantial custom application logic, or teams that want unrestricted visual page building.

Do we need a developer to use it?

Not for day to day content updates. You control who can edit what with roles and publishing guardrails. For theme work, you may want a front end developer or designer who is comfortable with HTML, CSS, JavaScript and templating. No back end development is required for normal site delivery.

Can we use our own JavaScript libraries?

Yes. RealMosaic does not require a front end build stack for normal sites. There is a small default JavaScript footprint for common behaviour such as form handling, and you can add your own libraries and scripts per page or across a theme as needed.

Are new modules and tools coming?

Yes. RealMosaic is in active rollout and modules are added based on agency demand and proven use cases. Module availability, scope and Unit weight are confirmed during scoping.

Can we use our own theme?

Yes. Themes are designed for reuse across multiple client sites. Start with a base theme, then customise per client where needed using HTML, CSS, JavaScript and RealMosaic templating.

Do changes require a build or deployment?

Not for normal work. Theme changes happen inside the CMS, with save and publish steps, history, comparison and restore. You can use plain HTML, CSS and JavaScript without running a separate front end build process.

What does capacity in Units mean?

Units measure capacity across your whole client portfolio. Each site uses a base amount, then uses more only when it includes specialist modules or exceeds published resource thresholds such as content volume, storage or bandwidth.

Are these prices retail or wholesale?

They are agency and partner prices. Agencies can set their own client pricing for support, governance and ongoing improvements.

Is there a lock in contract?

No long contracts are required for platform access. If a client leaves, content can be exported, but moving to another CMS still requires a planned migration.

Can you help us migrate an existing website?

Yes. Migration scope depends on the content structure, asset volume, redirects and how much you want to standardise. During onboarding we map the current site into page layouts and a rollout plan.

What does early access mean?

Onboarding is limited and guided. The focus is stability, feedback and getting your first sites live cleanly before scaling further.

How do updates work?

Updates follow a disciplined release process and are designed to minimise surprises. The focus is predictable change rather than frequent breaking shifts.

How do you handle security?

Platform security is built around clear boundaries, account authentication, role based access and site isolation. Agencies remain responsible for user access, client permissions and publishing practices.

Security overview

Can Subtle Difference help with implementation?

Yes. Some agencies want platform access only, while others want implementation support. Subtle Difference can help with theme builds, migrations and ongoing improvements.

What is the typical onboarding timeline?

Timing depends on the theme approach, content volume and migration complexity. During onboarding we define the first site, page layouts and rollout sequence before expanding to additional sites.