More
Сhoose

Atlas Studio

A source-aware foundation for building access-controlled analytical microsites from heterogeneous public and institutional data.

Year: 2026 Analytical microsites Data lineage Decision support Proprietary

Product thesis

Public and institutional datasets are often available without being operationally comparable. Sources use different geographic keys, reporting periods, granularities, missing-value conventions, and publication formats. A dashboard cannot resolve those differences if its calculations and source cuts are hidden from the people interpreting it.

Atlas Studio is a proprietary, source-available foundation for building focused analytical microsites in which source preparation, methodology, service contracts, and presentation remain separate and inspectable. Its current Mexico public-security study is the working reference implementation, not a universal or production-certified platform.

Atlas Studio is an independent Hadox and Polisplexity product. It is not an official public-security service or government product, and it is not endorsed by any institution represented in its source material.

What the reference product demonstrates

The working repository covers a complete path from identified sources to a controlled analytical experience:

  • source acquisition, caching, normalization, and documented quality flags;
  • state and pilot-level comparisons using explicit rates, weights, benchmarks, and rankings;
  • protected study and state-detail API contracts;
  • React and D3 surfaces for matrices, trends, drivers, budget views, tables, and narrative;
  • account activation, viewer and administrator roles, password recovery, and basic usage telemetry; and
  • a multi-stage container that serves the compiled interface and API from one Node.js process.

The reusable value lies in that delivery pattern. New studies should define their own sources, dimensions, scoring rules, caveats, and visual surfaces without weakening a shared access, audit, and deployment boundary.

Architecture and analytical boundary

The reference implementation separates build-time data pipelines, generated study datasets, analytical services, Express API contracts, and the React presentation layer. The browser receives curated payloads rather than raw source archives, and the score remains decomposable into documented dimensions and weights.

The present single-instance identity store and local mail outbox are suitable for a controlled prototype, not a multi-tenant production service. Production use requires a transactional identity store, centralized authorization, rate limiting, account lockout and MFA, independent security tests, durable audit and deletion workflows, encrypted backups, and operator-managed TLS and perimeter controls.

Responsible interpretation

The current study combines public-safety incident rates and budget measures from different reference periods. Its results are comparative analytical devices, not causal findings, guarantees of policy effectiveness, complete measures of crime, or individual-level predictions. Higher expenditure is treated as capacity rather than proof that spending caused an outcome.

Every future microsite needs an explicit source register, transformation lineage, known limitations, validation owner, update policy, and reviewable methodology appropriate to its domain.

Maturity and next steps

Atlas Studio is a functional product prototype and early platform foundation. Priority work includes extracting study definitions from hard-coded implementation, moving identity and audit state to production-grade services, adding tenant and study-level authorization, automating source-quality and security checks, validating methodology independently, and proving the pattern with a second analytical vertical.

Licensing and public repository

The public repository contains working software and documentation for transparency, portfolio review, and technical evaluation. It is proprietary and source-available, not open source. Public visibility does not grant rights to copy, modify, distribute, host, resell, or create derivatives beyond the repository's license.

Third-party software, data, names, and marks remain subject to their respective rights and terms. References to public institutions and source publishers identify evidence provenance and do not imply sponsorship or endorsement.