System Architecture
System Architecture Overview
Vora's architecture is designed to deliver three properties simultaneously: the usability of a modern SaaS application, the trust guarantees of blockchain infrastructure, and the scalability required to serve governance communities ranging from 100 participants to millions. Achieving this combination requires a carefully layered architecture where each layer is optimized for its specific function and communicates with adjacent layers through well-defined interfaces.
This section provides a high-level overview of Vora's architectural approach. Detailed treatments of the blockchain transparency layer and security architecture follow in subsequent sections.
Architectural Principles
Vora's architecture is governed by five principles that inform every design decision:
1. Separation of Concerns
Governance logic, user experience, blockchain interaction, and data management are implemented as distinct layers with clear boundaries. This separation ensures that each layer can be independently optimized, scaled, and upgraded without cascading effects on other layers. It also enables the Web 2.5 user experience: the presentation layer operates at Web2 speed and polish, while the blockchain layer operates asynchronously, anchoring governance records without imposing latency on the user experience.
2. Progressive Decentralization
Vora's current architecture occupies a deliberate position on the centralization-decentralization spectrum. The user-facing application and governance logic are centralized for performance, reliability, and user experience quality. The governance record layer is decentralized, anchored to public blockchains that neither Vora nor any single entity controls. This hybrid model delivers the practical benefits of centralized application design (speed, usability, operational control) while providing the trust benefits of decentralized record-keeping (immutability, independent verifiability, censorship resistance).
Over time, Vora's architecture is designed to progressively decentralize additional components as the technology and ecosystem mature. The current architecture establishes the trust foundation; future iterations will expand the scope of decentralized guarantees.
3. Gasless Abstraction
All blockchain interactions are abstracted from the end user. Vora's infrastructure sponsors every on-chain transaction, manages key custody, and handles the complete lifecycle of blockchain interactions without requiring any action from voters or governance participants. This gasless abstraction is not a convenience feature --- it is an accessibility requirement. Customer governance cannot achieve universal adoption if it requires participants to understand wallets, gas fees, or blockchain mechanics.
4. Tier-Appropriate Infrastructure
Vora's architecture scales across four pricing tiers, with infrastructure capabilities calibrated to each tier's needs:
Application
Shared multi-tenant
Shared multi-tenant
Shared multi-tenant
Dedicated
Blockchain network
Base Mainnet
Base Mainnet
Base Mainnet
Ethereum Mainnet
Vote recording
Individual transactions
Merkle tree batching
Merkle tree batching
Merkle tree batching
RPC infrastructure
Shared
Shared
Shared
Dedicated (AWS Managed Blockchain)
Data residency
Platform-managed
Platform-managed
Platform-managed
Configurable
This tiered approach ensures that every organization receives blockchain-verified governance at every price point, while Enterprise clients receive the additional infrastructure isolation, security, and configurability that their requirements demand.
5. Auditability by Design
Every governance action in Vora produces a verifiable record. This is not a feature that was added to the architecture --- it is a property that the architecture was designed to produce. The system is constructed such that governance data flows inevitably toward on-chain anchoring, and every on-chain record can be traced back to the governance action that produced it.
High-Level Architecture
Vora's system architecture is organized into four primary layers:
Presentation Layer
The presentation layer provides the user interface through which governance designers (brand administrators) and governance participants (customers, community members) interact with the platform. This layer is responsible for:
Governance space management and configuration
Proposal creation, management, and monitoring
Voting interfaces optimized for clarity and accessibility
Idea Challenge submission and evaluation interfaces
Analytics dashboards and data visualization
Badge and XP progression displays
Administrative controls and user management
The presentation layer is implemented as a modern web application following current best practices for performance, accessibility, and responsive design. It communicates with the governance layer through a well-defined API, ensuring clean separation between user experience and business logic.
Governance Layer
The governance layer implements Vora's core governance logic. It is the computational engine that manages:
Proposal lifecycle management: State transitions (Draft, Active, Closed, Executed, Cancelled), ending condition evaluation, and outcome determination
Voting strategy execution: Implementation of all seven voting strategies, including vote validation, weight calculation, and result aggregation
Access control: Voter eligibility verification across all three access modes (Whitelist, Public, Badge Earner)
Gamification engine: XP calculation, badge threshold evaluation, governance level segmentation
Analytics computation: Real-time calculation of governance metrics, Shannon Entropy, Passion Index, and governance levels
Challenge management: Idea Challenge lifecycle, submission workflows, and winner determination
The governance layer is designed for correctness, consistency, and auditability. Every governance action produces a structured event that flows to both the data layer and the blockchain layer, ensuring that governance records are simultaneously available for real-time application use and permanent on-chain anchoring.
Data Layer
The data layer manages the persistent storage of governance data in a format optimized for application performance. This layer handles:
Governance space configurations and metadata
Proposal definitions and state
Vote records and aggregations
User profiles, XP balances, and badge holdings
Analytics data and computed metrics
Integration configurations and webhook management
The data layer operates with strict consistency guarantees to ensure that governance data is never lost, corrupted, or inconsistently represented. It is designed for high-availability and disaster recovery, with infrastructure-level redundancy appropriate to each pricing tier.
Blockchain Layer
The blockchain layer is Vora's trust anchor. It is responsible for recording governance actions on public blockchain infrastructure in a manner that is immutable, independently verifiable, and cryptographically secure. The blockchain layer handles:
Vote recording: Individual transaction minting or Merkle tree batch aggregation, depending on tier
Result certification: On-chain recording of proposal outcomes when proposals close
Gas management: Sponsorship and optimization of all on-chain transaction costs
Proof generation: Creation of cryptographic proofs (Merkle proofs) that enable per-vote verification even within batched transactions
Smart contract interaction: Communication with the VoteAuditLog contract and related on-chain infrastructure
The blockchain layer is described in detail in the Blockchain Transparency Layer section.
Cross-Cutting Concerns
Integration Layer
Vora's integration layer provides the interfaces through which external systems interact with the platform:
REST API: Programmatic access to governance data, proposal management, and participant administration. The API supports the full lifecycle of governance operations and is designed for integration with existing brand technology stacks.
Webhooks: Real-time event notifications pushed to configured endpoints when governance events occur. Supported events include Vote Cast, Proposal Created, and Proposal Status Changed. Webhooks enable brands to build real-time workflows that respond to governance activity.
CRM connectors: Pre-built integrations with major CRM platforms (Shopify, HubSpot) that synchronize governance data with customer relationship management systems.
Member import: CSV and API-based import mechanisms for onboarding existing customer databases into governance spaces.
Notification Service
The notification service manages the delivery of governance communications across email and SMS channels. It handles:
Template management for brand-customized governance notifications
Delivery scheduling and throttling
Channel selection logic (email vs. SMS based on configuration and urgency)
Delivery confirmation and retry logic
Analytics Engine
The analytics engine continuously processes governance data to produce the real-time metrics, visualizations, and insights that power Vora's analytics dashboards. It computes:
Aggregate governance metrics (total proposals, total votes, unique voters, participation rates)
Governance level segmentation (Platinum, Gold, Silver, Bronze)
Shannon Entropy for consensus/polarization analysis
Passion Index for Multiple Vote strategy proposals
Trend analysis and historical comparisons
Scalability Architecture
Vora's architecture is designed to scale across multiple dimensions:
Participant scale. From 100 users (Starter tier) to unlimited users (Enterprise tier), the architecture must handle governance spaces with vastly different population sizes without degradation.
Proposal scale. From 3 proposals per month to unlimited, the system must manage varying governance activity levels without performance impact.
Blockchain throughput. The Merkle tree batching system is designed to scale on-chain throughput efficiently. By aggregating up to 50 votes per on-chain transaction, the system achieves a 50x improvement in blockchain throughput per transaction while maintaining per-vote verifiability through Merkle proofs.
Geographic distribution. The platform infrastructure is designed for global performance, with content delivery and compute resources distributed to minimize latency for governance participants regardless of location.
Reliability and Availability
Governance is a high-integrity function. A vote that fails to record, a proposal that disappears, or a result that is inconsistent undermines the trust that is Vora's core value proposition. The architecture is designed for:
High availability. Multi-zone deployment with automated failover ensures that governance services remain accessible during infrastructure disruptions.
Data durability. Governance data is replicated and backed up with recovery point objectives appropriate to its criticality. On-chain records provide an additional durability guarantee: even in the event of a catastrophic platform failure, governance records anchored to the blockchain remain permanently accessible.
Consistency guarantees. The governance layer implements strict consistency protocols to ensure that vote counts, XP balances, and governance outcomes are never inconsistent, even under concurrent access.
Enterprise tier deployments receive additional reliability guarantees through dedicated infrastructure, custom SLAs, and isolated compute and storage resources.
Technology Decisions
Vora's technology decisions are guided by pragmatism and fitness for purpose. The platform leverages:
Ethereum ecosystem blockchains (Base Mainnet and Ethereum Mainnet) for governance record anchoring, selected for their security track record, developer tooling maturity, and block explorer availability.
Modern web application frameworks for the presentation layer, selected for performance, developer productivity, and accessibility compliance.
Cloud-native infrastructure with provider-grade security, availability, and compliance certifications (SOC2-grade).
Purpose-built analytics infrastructure optimized for the real-time computation requirements of governance metrics.
Specific technology choices at the implementation level are proprietary and not detailed in this document. The architectural principles and layer responsibilities described above represent the stable, long-term structure of the system. Implementation details evolve as technology matures and operational requirements change.
Last updated