title: "How We Built SIGNALS — From Whitelist Tool to Full Desktop-OS SaaS" date: "2026-03-22" description: "The technical story of scaling SIGNALS from a simple whitelist manager to a multi-tenant platform serving 156K+ users across 9 live portals on Base." tags: ["web3", "saas", "engineering"]

How We Built SIGNALS

What started as a whitelist tool in 2024 became the largest creator economy platform on Base. Here's the technical story.

The Problem

Every Web3 project needed the same infrastructure: whitelisting, task management, referrals, leaderboards, analytics. Teams were rebuilding the same systems from scratch, spending months on infrastructure instead of their actual product.

The Architecture

SIGNALS runs as a multi-tenant SaaS — one codebase, 9 live portals. Each portal gets its own domain, branding, task configuration, and user base, but shares the core engine.

The key architectural decisions:

• Tenant isolation at the data layer — every query is scoped by portal ID. No data leaks between tenants.
• Plugin-based task system — 30+ task types (social follows, contract interactions, quiz completions, referrals) all implement the same interface. Adding a new task type means adding one file.
• Desktop-OS UI pattern — 32 apps running in a window manager. Users feel like they're using an actual operating system, not a web app.

The Numbers

After 18 months of building:

• 156K+ users onboarded across all portals
• 1.6M tasks completed
• 1.1B+ points distributed
• 800+ ETH raised through the ecosystem
• 30+ ICM partners integrated

What I Learned

Building a multi-tenant system at this scale taught me that the boring infrastructure decisions matter most. Rate limiting, caching strategies, database indexing, tenant scoping — these aren't glamorous, but they're the difference between a platform that scales and one that falls over.

The other lesson: ship the simplest version first. SIGNALS v1 was literally just a whitelist form. Every feature we added was in response to real user demand, never speculation.

More technical deep-dives coming soon. Follow @duhhhdev for updates.