Despliegue

Guía de Despliegue

Elija el modelo de despliegue que se ajuste a sus requisitos de seguridad.

Deployment lanes

Keep the operator surface consistent while you decide where compute, storage, and identity boundaries belong.

Supported deployment lanes

4 models

Core data plane

Postgres + Neo4j

Object storage compatibility

R2 / S3

Identity integration posture

SSO-ready

Architecture brief

Choose the boundary that matches your residency, accreditation, and operating model

Deployment planning should clarify where the data sits, who operates the environment, and how observability, storage, and identity controls are partitioned before implementation starts.

Deployment model

Nube (SaaS)

Despliegue totalmente gestionado en nuestra infraestructura de nube segura.

Deployment model

On-Premise

Despliegue Public Safety dentro de su propio centro de datos.

Deployment model

Híbrido

Combine despliegues en nube y on-premise.

Deployment model

Nube Gubernamental

Despliegue certificado ENS en infraestructura aprobada.

Operator surface

Investigation workspace

The analyst-facing workflow stays consistent while the underlying residency and hosting model changes.

Arquitectura del Sistema

Core stack

Public Safety usa una arquitectura moderna, nativa de la nube.

Frontend Web

Next.js / Cloudflare Workers

Gateway de API

REST, GraphQL, and event services

Servicios de IA

Model routing and governed processing

Almacenamiento de Objetos

Object storage with evidence retention controls

Capacity planning

Requisitos del Sistema

Infrastructure sizing should reflect operator concurrency, ingestion load, evidence retention, and the models you expect to run in the environment.

Baseline

Mínimo (Despliegues Pequeños)

Use this lane for pilots, low-volume teams, or controlled proof-of-value environments.

  • 8 CPU cores
  • 32 GB RAM
  • 500 GB SSD storage
  • 1 Gbps network

Operational target

Recomendado (Empresarial)

Plan for this lane when multiple teams, heavier ingestion, or sustained analytics workloads are expected.

  • 32 CPU cores
  • 128 GB RAM
  • 2 TB NVMe storage
  • 10 Gbps network

Planning notes

What usually changes the size

The main drivers are document volume, evidence retention, graph depth, alerting frequency, and how much AI processing stays inside the boundary.

Telemetry

Operational analytics

Deployment planning should include the telemetry needed to watch usage, queue depth, and operational load after go-live.

¿Listo para Desplegar?

Contacte a nuestro equipo para discutir sus requisitos de despliegue.