Skip to content
@Oppulence-Engineering

OppulenceEngineering

Building a suite of financial tools to help the underserved small business owner

Oppulence Engineering

Revenue Operations OS - The first platform managing the complete revenue lifecycle from customer acquisition through payment recovery.

What We're Building

Oppulence is a Platform + Apps architecture for SMB SaaS companies:

┌──────────────────────────────────────────────────┐
│         DEVELOPER PLATFORM (Foundation)          │
│   Unified Financial API: Stripe, Plaid, Banks    │
└──────────────────────────────────────────────────┘
                        │
         ┌──────────────┼──────────────┐
         ▼              ▼              ▼
   ┌──────────┐   ┌──────────┐   ┌──────────┐
   │  POLAR   │   │  CANVAS  │   │  FUTURE  │
   │ Billing  │   │ Dunning  │   │   APPS   │
   └──────────┘   └──────────┘   └──────────┘

Revenue OS Diagrams

These Mermaid diagrams outline component roles, communication frameworks, and key flows across the Unified Revenue OS, the data plane, and BillFlow AP.

graph LR
  subgraph Core_Apps
    Oppulence[Oppulence - Monetization]
    Canvas[Oppulence Canvas - Recovery]
    BillFlow[BillFlow AP - Payables UI]
  end

  subgraph Data_Plane
    CanvasAPI[Canvas API]
    Worker[Canvas Worker]
    UnifiedAPI[Developer Platform - Unified API]
    Sync[Stripe Sync Engine]
    Storage[Oppulence Storage]
    Bus[Event Bus - Queue]
  end

  subgraph Data_Stores
    PG[(Postgres)]
    CH[(ClickHouse)]
    Obj[(Object Storage)]
  end

  subgraph External
    Stripe[Stripe]
    Email[Email Inbox]
    Vendors[Vendor Portals]
    Accounting[QBO Xero NetSuite]
    Bank[Bank ACH]
  end

  Oppulence --> CanvasAPI
  Canvas --> CanvasAPI
  BillFlow --> UnifiedAPI
  BillFlow --> Storage
  Oppulence --> UnifiedAPI
  Canvas --> UnifiedAPI

  CanvasAPI --> Bus
  Bus --> Worker

  Sync <--> Stripe
  Sync --> PG
  Sync --> CH

  Storage --> PG
  Storage <--> Obj
  Email --> Storage
  Vendors --> Storage

  UnifiedAPI <--> Accounting
  UnifiedAPI <--> Bank

  CanvasAPI --> Sync
  BillFlow --> Sync
  Oppulence --> Sync
Loading
graph TD
  Stripe[Stripe] -- Webhooks --> Sync[Stripe Sync Engine]
  Sync -- Normalized events --> Bus[Event Bus / Queue]
  Sync -- SQL writes --> PG[(Postgres)]
  Sync -- Analytics writes --> CH[(ClickHouse)]

  Email[Email Inbox] -- Forward/IMAP --> Storage[Oppulence Storage]
  Vendors[Vendor Portals] -- API pulls --> Storage
  Storage -- OCR/Extraction --> BillFlow[BillFlow AP]

  BillFlow -- HTTP API --> UnifiedAPI[Developer Platform]
  UnifiedAPI -- OAuth + REST --> Accounting[QBO Xero NetSuite]
  UnifiedAPI -- ACH/Bank APIs --> Bank[Bank ACH]

  Oppulence[Oppulence] -- HTTP API --> CanvasAPI[Canvas API]
  CanvasAPI -- Events --> Bus
  Bus -- Jobs --> Worker[Canvas Worker]

  CanvasAPI -- Query --> Sync
  BillFlow -- Query --> Sync
  CanvasAPI -- Docs/Contracts --> Storage
Loading
sequenceDiagram
  autonumber
  actor Customer
  participant Oppulence
  participant Stripe
  participant Sync as Stripe Sync Engine
  participant Bus as Event Bus / Queue
  participant CanvasAPI
  participant Worker as Canvas Worker
  participant Notify as Comms - Email SMS
  participant Unified as Developer Platform

  Customer->>Oppulence: Checkout / invoice
  Oppulence->>Stripe: Create charge/invoice
  Stripe-->>Sync: Webhook events
  Sync->>Bus: Publish normalized events
  Bus-->>CanvasAPI: Deliver billing events
  CanvasAPI->>Bus: Enqueue recovery workflow
  Bus-->>Worker: Run recovery job
  Worker->>Notify: Dunning / payment updates
  Worker->>Unified: Post status to accounting/CRM
Loading
sequenceDiagram
  autonumber
  actor Vendor
  actor Approver
  participant Email as Email Portal
  participant Storage as Oppulence Storage
  participant BillFlow
  participant Sync as Stripe Sync Engine
  participant Unified as Developer Platform
  participant Accounting as QBO Xero NetSuite
  participant Bank as Bank ACH

  Vendor->>Email: Send invoice
  Email->>Storage: Forward/upload
  Storage-->>BillFlow: Extracted invoice data
  BillFlow->>Sync: Match to Stripe charges
  BillFlow->>Approver: Request approval
  Approver->>BillFlow: Approve / reject
  BillFlow->>Unified: Initiate payment + sync
  Unified->>Bank: Pay vendor
  Unified->>Accounting: Create/update bill
Loading

Repositories

Repository Purpose Stack
oppulence-developer-platform Unified Financial API Go + TypeScript
oppulence Billing/Storefront Python/FastAPI
oppulence-canvas Dunning/Recovery TypeScript/Next.js
oppulence-sync-engine Stripe Data Sync TypeScript/Fastify

Architecture

See ARCHITECTURE.md for the full technical architecture.


Building the financial infrastructure for the autonomous economy.

Popular repositories Loading

  1. paperless-check-if-email-exists paperless-check-if-email-exists Public

    Forked from reacherhq/check-if-email-exists

    Check if an email address exists without sending any email, written in Rust. Comes with a ⚙️ HTTP backend.

    Rust

  2. reacher-js reacher-js Public

    Forked from reacherhq/reacher-js

    TypeScript wrapper library over Reacher API

    TypeScript

  3. .github .github Public

  4. design-system design-system Public

    TypeScript

  5. Desktop-Assistant Desktop-Assistant Public

    Forked from rowboatlabs/rowboat

    Open-source AI coworker, with memory

    TypeScript

  6. course-video-manager course-video-manager Public

    Forked from mattpocock/course-video-manager

    TypeScript

Repositories

Showing 6 of 6 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…