EtheReal
Product architecture

How EtheReal works

A look under the hood — flows, data, security, and the proprietary compatibility engine that powers every reading.

System overview

Web client

React · TanStack Router

API gateway

Edge functions

Database

PostgreSQL · RLS

Engine (sealed)

Black-box algorithm

Stripe + Tax

EU VAT, refunds

Resend email

Deliveries & receipts

Core flows

Compatibility reading
  1. 1Seeker submits both birth profiles
  2. 2Stripe checkout (suggested €6 · min €3)
  3. 3Engine API receives sanitized inputs
  4. 4Engine returns score + insight payload
  5. 5PDF generated · emailed via Resend
  6. 6Buyer redirected back with download
Astrologer session
  1. 1Seeker browses astrologers
  2. 2Picks date/time → Stripe holds amount
  3. 3Astrologer accepts in queue
  4. 4Session occurs · marked complete
  5. 5Funds released to payout balance
Referral & tier engine
  1. 1Seeker shares unique link
  2. 2Invitee signs up via referral cookie
  3. 3First purchase triggers reward credit
  4. 4Tier recalculated nightly (Stardust → Celestial)
Ebook purchase
  1. 1One-click Stripe checkout
  2. 2Order recorded · receipt emailed
  3. 3PDF + EPUB unlocked in dashboard
  4. 4Lifetime updates pushed to library
The compatibility engine

A sealed, server-side function. Inputs go in, scores come out — internal logic never leaves the runtime.

Inputs

· Profile A

· Profile B

· Intent

engine.run()

Outputs

· Score 0–100

· Axes (3)

· Narrative

Inputs — two birth profiles (date, time, place), optional intent ("romantic", "platonic", "creative").

Outputs — overall score, emotional/mental/spiritual axes, narrative summary, key aspects array.

Isolation — algorithm runs in a sandboxed container; no logs of internals; only signed releases deploy.

Replaceable — placeholder during dev; founder deploys the real bundle via a one-line CLI.

Data model

users

orders

readings

bookings

referrals

submissions

Security & GDPR

Row-level security

Users only see their own data; admin scoped through verified roles.

Encrypted at rest

AES-256 for PII; secrets rotated quarterly via a managed vault.

Delete on request

One-click GDPR purge across orders, readings, and submissions.