Back
Product Architecture

How Praeva works

A transparent look at the engines powering signup, referrals, status progression, and the members-only marketplace.

High-level system

Marketing site & landing
Pre-launch landing, signup capture, GDPR consent log, SEO + analytics.
Member portal
Dashboard, referrals, status, marketplace, profile.
Admin console
Member management, referral rules engine, reporting, exports.
API Layer
Versioned REST + webhooks, OpenAPI specced.
Rules Engine
Referral attribution, tier progression, anti-fraud.
Postgres
Members, referrals, listings, consent, audit log.
Notifications
Transactional email, in-app, milestone triggers.

Referral & status engine


   ┌──────────────┐      ┌────────────────┐      ┌──────────────────┐
   │  New signup  ├──────▶  Attribution   ├──────▶  Anti-fraud      │
   │  (with ref?) │      │  match ref code│      │  IP/device/email │
   └──────────────┘      └────────────────┘      └────────┬─────────┘
                                                          │
                                                  pass ◀──┴──▶ fail
                                                   │           │
                                          ┌────────▼─────┐ ┌───▼──────┐
                                          │ Credit       │ │ Quarantine│
                                          │ referrer +1  │ │ (manual)  │
                                          └────────┬─────┘ └───────────┘
                                                   │
                                          ┌────────▼──────────┐
                                          │ Tier rule check   │
                                          │ refs >= threshold?│
                                          └────────┬──────────┘
                                                   │ yes
                                          ┌────────▼──────────┐
                                          │ Promote · notify  │
                                          │ Founding→Insider  │
                                          │ →Patron→Legacy    │
                                          └───────────────────┘
            

Tier rules

Founding
0 referrals
Initial entry. Marketplace browse, profile.
Insider
5 referrals
Event RSVPs, monthly briefing.
Patron
15 referrals
Direct introductions, private dossiers.
Legacy
35 referrals
Roundtables, co-investment access.

Anti-fraud controls

Self-referral block
Same email or verified phone cannot be both referrer and referee.
Device & IP fingerprint
Hash-matched against historical signups.
Velocity caps
Per-IP, per-device, per-day signup throttles.
Manual review queue
Suspicious referrals held for admin review before crediting.

Marketplace flow

1
Provider creates listing
2
Admin reviews
3
Listing goes Active
4
Member inquires
5
Provider responds

Data model · core entities

Member
  • id
  • email
  • name
  • status
  • referral_code
  • referrer_id
  • consent_at
  • created_at
Referral
  • id
  • referrer_id
  • referee_id
  • channel
  • ip_hash
  • credited_at
  • status
Listing
  • id
  • provider_id
  • category
  • price
  • status
  • views
  • inquiries
Lead
  • id
  • listing_id
  • member_id
  • message
  • status
  • created_at
ConsentLog
  • id
  • member_id
  • policy_version
  • scope
  • timestamp
AuditEvent
  • id
  • actor_id
  • action
  • target
  • metadata
  • timestamp

Integrations

Email
Webhooks
CRM sync
OAuth / SSO