ComplyEaze Public
Public website, documentation, trust, release, policy, and brand surfaces for
the ComplyEaze product family.
This repository is intended to be open source. It is separate from the private
ComplyEaze application repository, which owns authenticated Axal workflows,
tenant data, credentials, document processing, portal automation, Prisma,
Redis/BullMQ workers, and production app deployment infrastructure.
Scope
In scope:
- Public ComplyEaze, Axal, Pack, Tools, and Sanchika pages.
- Public-safe docs, status, changelog, release, support, security, privacy, and
terms pages.
- SEO assets such as metadata, robots, sitemaps, canonical URLs, and social
preview assets.
- Synthetic examples and public review evidence.
Out of scope:
- Authenticated app routes and APIs.
- Tenant, workspace, client, credential, portal, document, or tax data.
- Private deployment secrets and infrastructure.
- Real taxpayer screenshots, files, identifiers, or portal responses.
Development
The public architecture is an incremental Astro workspace with independent
ComplyEaze, Axal, and Pack static apps. During P1, the existing generator remains
the customer-facing parity baseline while routes move app by app; it is deleted
only after route, metadata, link, and rendered parity are proven.
pnpm install --frozen-lockfile
pnpm dev:core
pnpm dev:axal
pnpm dev:pack
pnpm verify
Astro commands disable framework telemetry. Public pages target zero client
JavaScript unless a later reviewed interaction requires a small island. Preview
builds may set PUBLIC_SITE_ORIGIN; production origins remain the default in
each app configuration.
Governance
Public Pages
/about/ explains the public repo boundary and product-family proof model./contact/ routes public-site, security, and private-product inquiries without collecting form data./products/pack/ routes to Pack-owned source, release, privacy, security, and support facts without copying extension claims./products/tools/ routes to Tools-owned utility runtime and release evidence without copying utility implementation./privacy/ defines the public-repo privacy boundary./terms/ defines public-site and open-source usage boundaries./status/ reports repository and static-site readiness, not private app uptime./changelog/ records source-backed migration slices./release-evidence/ lists the evidence expected before release or cleanup.
