Marketplace / Blueprint 01
LIVEFoundation / automation

AICORTEX Core Platform

Deploy the owned AI substrate once, then add capabilities as modules.

Core: always presentReview my build

Interactive platform map

Architecture in context

The focused blueprint, its required foundation, and declared recommendations.

Core Selected Automatic Required path
Blueprint 01 / Foundation

AICORTEX Core Platform

Deploy the owned AI substrate once, then add capabilities as modules.

2 vCPU3 GB RAM6 services
Core: always presentView blueprint
01 / Problem

What this replaces

AI experiments become fragile collections of hand-built services, hidden dependencies, inconsistent networking, and undocumented recovery steps.

02 / Outcome

What your team gains

A repeatable private platform foundation with container lifecycle, pod networking, ingress, persistence, boot protection, deployment automation, and a consistent operating model.

03 / Capability

What is inside the blueprint

Podman container and pod lifecycle
Shared pod network namespaces and published-port ownership
Declarative Ansible deployment and configuration
Central Traefik routing and middleware
Persistent PostgreSQL data tier
Cloudflare Tunnel ingress pattern
Restart, boot, and health-check patterns
Backup/recovery and dependency pinning patterns
04 / Architecture

How it fits the platform

Linux/Alpine host -> Podman pods and standalone edge services -> Traefik -> application/data services; Ansible is the deployment authority and configuration source of truth.

Included services

Podman, Ansible, Traefik, PostgreSQL, cloudflared, nginx

Platform requirements

Core foundation only.

05 / Delivery

From prerequisites to operation

Prerequisites
  1. Linux host/VPS with adequate CPU, RAM and storage
  2. DNS/domain control
  3. Administrative access
  4. Persistent storage locations
  5. Outbound internet access where cloud providers are used
Deployment
  1. Bootstrap Podman and Ansible deployment container
  2. Create base network/pod topology and persistent paths
  3. Deploy Traefik and Cloudflare Tunnel
  4. Provision shared database tier and application roles
  5. Apply boot/restart/health protections
  6. Run reconciliation checks after deployment
Configuration
  1. Domains and route inventory
  2. Storage paths and retention
  3. Database names/users/schemas
  4. Resource limits
  5. Restart and health-check policy
  6. Cloudflare tunnel routes
  7. Backup targets and schedules
Operations
  1. Monitor disk, memory, swap and container health
  2. Verify boot units after changes
  3. Pin critical dependencies and image versions
  4. Test restore procedures
  5. Reconcile declared vs running state
07 / Technology

Technology behind this capability

PostgreSQLRUNNING - three separate DB instances in censusTraefikRUNNING - only ingress pathCloudflare TunnelRUNNINGPodmanRUNNING - 61 containers/15 pods in censusAnsibleRUNNING in deployment containernginxRUNNING in frontend and static sites