Celestium — Astrology Engine, App & Natal Product

The Problem

A premium natal product needs a real engine behind it. Off-the-shelf astrology APIs are either limited, expensive at scale, or don’t expose the structured data needed for archetypal synthesis. And most natal products fall into two buckets: free auto-generated reports that feel mechanical, or expensive bespoke readings that don’t scale. Building the engine in-house meant control over precision, interpretation surfaces, and the long tail of features (astrocartography, transits, human design, tarot) that competitors silo into separate products — and it opened a middle path for the product: the depth of a curated reading with the consistency of a real engine behind it.

The Solution

A four-module Swift package, wrapped in a SwiftUI app and packaged into a productized offering:

• CelestiumEngine — core astrological computation: natal charts, transit synthesis, astrocartography, human design, tarot deck. Includes a comprehensive interpretation layer (transit angle meanings, traditional astrology audit harness).
• CelestiumApp — the SwiftUI shell that presents readings to the user.
• CelestiumUI — shared design system and view components.
• CelestiumCLI — command-line surface for batch generation and testing.

On top of the engine sits the premium natal product: an 8-archetype offering where each chart is matched to a primary archetype and a secondary modulation, with interpretation written through the lens of how those archetypes interact across the houses, aspects, and elemental signatures of the chart. Two SKUs — a standard archetypal portrait and a premium deep-dive with transit weather and the next 12 months of unfolding themes.

Tests live alongside each module — including an astrology standards audit that verifies the engine’s output against canonical references.

Status

Live on the App Store for iPhone, iPad, and Mac (iOS 1.0.1 + macOS 1.0.0). The CLI is operational for batch generation (used by the natal product fulfillment pipeline), and the engine and interface keep iterating release over release. The archetypal product is refining its interpretation surface, delivery pipeline, and buyer experience.

What This Demonstrates

Building the substrate, not just consuming an API. Owning the engine means the product can evolve without renegotiating with a vendor every time the interpretation surface changes — and the same engine powers the consumer app, the product fulfillment pipeline, and any future surfaces. The bet is that the judgment behind a meaningful natal reading can be encoded into archetypes and an engine, with the human-curated layer kept where it actually matters.