Compatibility

Summary of the current compatibility posture for Pharos Framework.

Database support

Pharos currently supports:

SQLite
PostgreSQL

Dynamic apps are database-driven by default. Runtime scratch JSON exports are operational surfaces, not the primary source of truth when a relational backend is active.

Deployment Layout

Packaged deployments expect:

Pharos runtime at /usr/local/bin/pharos
configuration under /etc/pharos
app bundles under /srv/pharos/apps
database files under /var/lib/pharos by default
runtime state under /var/state/pharos

Host and runtime model

Pharos supports two main app hosting profiles:

static-pages
dynamic-app

static-pages apps are fully materialized build artifacts.

dynamic-app apps are served through the shared Pharos runtime and can combine declarative templates, fixtures, generated CRUD surfaces, and database-backed state.

Browser and HTTP posture

Pharos is designed around normal browser-hosted HTTP applications with:

health and readiness probes
CSRF protection for framework-owned flows
app-local base paths such as /ucal or /dev_docs
shared runtime logging and error reporting

Build and release targets

The release archive currently carries native runtime support and release validation for these target families:

Linux x86_64 GNU
Linux x86_64 musl
Linux ARM64 GNU
macOS universal
Windows x86_64 MSVC
Windows ARM64 MSVC