Built on AWS

Blurtopian's contributor rewards platform is powered by a multi-service AWS stack — purpose-built for scalability, reliability, and global reach. This page documents each layer of the architecture and the role AWS plays in running the platform end-to-end.

▲ Amazon Web Services Partner Infrastructure
System Architecture Diagram

Each layer maps to a distinct responsibility. AWS services handle compute, storage, analytics, and content delivery. The Blurt blockchain handles reward distribution.

Clients
🌐
Web / Mobile
Contributors

Submit work via blurtopian.com

📁
Web / Mobile
Project Owners

Post announcements, manage projects

Web
Moderators

Review and approve contributions

HTTPS requests · REST API calls
CDN
AWS CloudFront
Content Delivery Network

Caches static assets and API responses globally across edge locations

Cache miss → origin · API pass-through
Compute
🖥
AWS EC2
REST API Server

Hosts api.blurtopian.com — handles all submission, moderation, and rewards endpoints

λ
AWS Lambda
Analytics Pipeline

Event-driven functions aggregate stats, calculate moderator rewards, power /api/stats

Reads / writes · SQL queries · event triggers
Data
🚗
AWS RDS
PostgreSQL Database

Stores users, contributions, moderation decisions, reward records, project config

Approved contributions → reward transactions
Rewards
Blurt Blockchain
Reward Distribution

Proof-of-Brain consensus distributes BLURT tokens to approved contributors after 7 days

📉
GitHub API
git_archiver Integration

Verifies pull requests, forks, and open source contribution authenticity

AWS Services in Detail

Each AWS service was chosen to solve a specific platform requirement. Here's what each one does and why it was the right choice.

AWS EC2

Elastic Compute Cloud

Role in the platform
API Server — the backbone of all platform operations

EC2 hosts the Blurtopian REST API at api.blurtopian.com. Every action on the platform — submitting a contribution, triggering a moderation review, fetching project posts, loading moderator profiles — is handled by this API layer. EC2 was chosen for its flexibility to run a persistent, stateful Node.js API server with full control over networking and scaling.

  • POST /api/posts/ — accepts new contribution submissions from contributors
  • GET /api/posts/ — returns paginated, filtered contributions per project (sorted by votes, date, or payout)
  • GET /api/stats — returns aggregated platform metrics: total authors rewarded, total rewards distributed, pending payouts
  • GET /api/moderators — returns moderator profiles with their pending and historical reward totals
  • Connects to RDS PostgreSQL over a private VPC subnet for secure, low-latency database access
AWS RDS

Relational Database Service

Role in the platform
PostgreSQL — all platform state and history

RDS runs the PostgreSQL instance that stores every piece of platform data. Using a managed database service eliminates the operational overhead of patching, backups, and failover — critical for a platform where contributor reward records must never be lost. Multi-AZ deployment ensures high availability.

  • Users table — contributor and moderator accounts, reputation scores, linked GitHub/Blurt usernames
  • Contributions table — all submitted work with type, project, status (pending / approved / rejected), timestamps
  • Moderation records — who reviewed each submission, decision, notes, and rule category applied
  • Rewards ledger — author payout amounts, curator shares, moderator allocations, payout dates
  • Projects table — configuration for each listed open source project, GitHub IDs, reward rules
AWS Lambda

Serverless Analytics Pipeline

Role in the platform
Event-driven functions that power platform analytics and reward stats

Lambda functions run on a scheduled basis and in response to platform events to compute aggregate statistics. Because these workloads are periodic and short-lived, Lambda is significantly more cost-efficient than running dedicated compute for analytics tasks.

  • Stats aggregator — queries RDS to compute total_paid_authors, total_paid_curators, total_pending_rewards, total_paid_rewards and caches the results for the /api/stats endpoint
  • Moderator reward calculator — distributes 5% of contributor reward pool proportionally across active moderators based on review volume
  • Payout processor — monitors the Blurt blockchain for 7-day payout events and records finalized reward amounts back to RDS
  • Contribution quality scorer — runs validation rules against new submissions before they enter the moderation queue
AWS CloudFront

Content Delivery Network

Role in the platform
Global CDN — low-latency delivery for a worldwide contributor base

Blurtopian serves contributors across the globe — Southeast Asia, Europe, Latin America, and beyond. CloudFront ensures that static assets (the Vue.js frontend, CSS, JavaScript, and project images) are delivered from the nearest edge location, keeping load times fast regardless of where contributors are located.

  • Frontend caching — serves the blurtopian.com Vue.js SPA from edge nodes, reducing latency globally
  • API response caching — caches /api/stats and project listing responses to reduce EC2 load on high-traffic periods
  • Project image delivery — distributes project banner images and contributor avatars efficiently at scale
  • HTTPS termination — enforces HTTPS at the edge for all client traffic, with automatic certificate management via ACM
How a Contribution Moves Through the Platform

From the moment a contributor submits their work to the moment they receive a reward, every step passes through the AWS infrastructure. Here's the full journey.

1
Contributor submits work CloudFront

The contributor fills out a submission form on blurtopian.com. The page and its assets are served from the nearest CloudFront edge location.

2
API receives the submission EC2

The form data hits the EC2-hosted REST API at api.blurtopian.com. The API validates the payload, checks the contributor's account, and writes the submission to the database.

3
Submission stored and queued RDS

PostgreSQL on RDS records the contribution with status pending. The moderation queue is updated so an available moderator sees it next.

4
Moderator reviews and decides EC2 RDS

A moderator loads the queue via the API (EC2), reviews the work against category rules, and submits their decision. The result is written to the moderation records table in RDS.

5
Analytics updated Lambda

An approval event triggers a Lambda function that recalculates platform-wide stats and updates the cached /api/stats response. A second function recalculates moderator reward shares.

6
Reward distributed via Blurt blockchain

Approved contributions are published to the Blurt blockchain. After 7 days, the community's votes determine the final payout. Lambda monitors the blockchain and records the finalized amount back to RDS.

7
Contributor redeems rewards

The contributor sees their earned BLURT in their wallet. The reward is traceable back through the full audit trail stored in RDS.

AWS Services at a Glance
Platform Area AWS Service What it does Why AWS
REST API EC2 Hosts api.blurtopian.com — contributions, moderation, rewards, moderator endpoints Full control over runtime, networking, and persistent connections to RDS and the Blurt blockchain node
Database RDS PostgreSQL Stores all users, contributions, moderation decisions, and reward ledger Managed backups, Multi-AZ failover, and automated patching — no DBA overhead for a small team
Analytics Lambda Aggregates platform stats, calculates moderator rewards, processes blockchain payout events Pay-per-invocation pricing is ideal for scheduled, short-lived analytics jobs with irregular traffic
Content Delivery CloudFront Serves frontend, caches API responses, delivers project images globally Blurtopian's user base spans 5+ continents — edge caching is essential for acceptable load times
Reward Distribution Blurt Blockchain Distributes BLURT tokens to approved contributors via community voting (Proof-of-Brain) Decentralized, transparent reward mechanism — no platform funds needed to pay contributors
Contribution Verification GitHub API Verifies pull requests, forks, and contribution authenticity via git_archiver First-party verification source for open source contribution proof