Pharos Platform Vision

Pharos was built from a simple idea: make web apps easier to build. Instead of assembling different languages and tools, you describe what you need in declarative YAML, SQL, and template files. The framework handles the rest.

Pharos 0.8.2 is the current package line for ongoing QA and release validation. The public source release is still pending, but the framework, CLI, packaged apps, generated surfaces, database backends, payment-provider flow, and shared runtime docs are public-facing and ready to review.

Model-driven app builder

Architect is the model-driven app builder for Pharos. Describe what you want in plain language, attach context when useful, and Architect turns that brief into a structured Pharos app model before generating source and running local validation.

The goal is not to replace developers. It is to remove the friction of setup and boilerplate while keeping the generated app inspectable. You focus on what your app should do; the builder produces declarations, source, and validation evidence that a developer can review and extend.

UI Design Studio

A companion app to help you design your app's UI. Let Architect create the app boilerplate, then edit it in a separate WYSIWYG editor. Make clean modern interfaces and SPAs. Includes a curated selection of icons for making UI components in a universally relatable style.

Auto-translation

Pharos will translate your app's text into multiple languages automatically. Declare which languages you support. Pharos detects text in your templates and fixtures, translates it, and serves the right version to each user.

No third-party translation services to manage. No manual string files. Just declare your languages and let the framework handle the rest.

Database options

Pharos now supports SQLite, PostgreSQL, MySQL, and MongoDB as database backends, with Redis available as an optional runtime cache layer.

Each backend connects through a stable framework-owned interface so apps can adopt it through configuration and compatible declarative contracts instead of rewriting app-owned request handling. Future backend expansion can continue from that same contract model.

Payment-provider interface

Pharos now includes an initial reusable payment-provider interface. Apps declare owner mapping, policy gates, checkout actions, return paths, and provider wiring in app-owned files while the runtime owns provider state, encrypted credential storage, callback validation, webhook handling, audit events, and fulfillment gating.

Stripe is the first concrete provider. Beacon Beats and UCAL can use demo mode or live Stripe-backed checkout depending on owner credentials and checkout mode.

OAuth / OIDC login

Pharos supports OAuth 2.0 authorization-code login with OpenID Connect through a framework-owned contract. You configure the provider, app routes, and templates; Pharos handles provider validation, local identity linking, and secure session issuance.

No third-party auth libraries. No vendor lock-in. One config block per provider.

Expanded multi-app hosting

Pharos already runs multiple apps under one process with different URL paths and shared runtime infrastructure. The next step is tighter integration: shared authentication between apps, cross-app workflows, and unified monitoring without per-app server management.

The long view

The roadmap is straightforward: every feature that can be shared across apps should live in the framework, not in app code. That is where Pharos is headed. More capability per deploy. Less to rebuild each time.