Modules and relationships

A clear boundary for every product and capability.

Atlas is modular by design. The cards below state what each capability does, its current readiness and whether access is foundational, optional or separately controlled.

01
Standalone foundation

Property Identity

A persistent property identity with source-backed facts, provenance, documents, uncertainty states, controlled history, sharing and handover.

Current readiness
Controlled-pilot ready
Inclusion
Foundation; separately controlled product
02
Separate module

Property Compliance

Organises compliance-related evidence, missing records, dates, inspections and review activity. It does not certify legal compliance.

Current readiness
Separately gated
Inclusion
Optional; not automatically included
03
Controlled Atlas module

Atlas Opportunities

Uses a signed, bounded relationship with the separately controlled Land Opportunity Finder engine. No opportunity is guaranteed or universally available.

Current readiness
Demonstrated in controlled Preview
Inclusion
Optional; workspace and entitlement required
04
Separate products

Operational relationships

SiteHQ and Verified Dispatch remain separate products. Any Atlas connection is optional, approved and bounded; Verify Presence is independent.

Current readiness
Relationship-specific evidence required
Inclusion
Not included by default
Separate means separate

Marketing language does not collapse ownership or authority.

Land Opportunity FinderA separately controlled specialist engine used through the bounded Atlas Opportunities relationship.

SiteHQA separate construction operating system; not automatically included in Atlas.

Verified DispatchA separate controlled-dispatch product; relationships must be specifically supported.

Verify PresenceAn independent AI Presence Management product, not an Atlas module.

Controlled pilot

Discuss a controlled Atlas pilot

We will confirm the organisation, workspace, property and module boundaries before any access is proposed.