The engine behind the work
One engine. Many purposeful systems.
Evo is a modular PHP engine for turning real operational rules into secure, multilingual systems—without rebuilding identity, governance, data, and observability every time.
Built from the same parent engine, shared contracts, and composable ecosystem sources used by the project family below.
Identity & access
Data & lifecycle
Web experiences
Operations
What Evo is
A foundation for serious systems, not a one-off app.
The engine separates reusable platform concerns from each product's domain. Teams inherit the same disciplined core, then shape the experience around the people and work the product serves.
Composable by design
Begin with a governed core, then compose only the domain ecosystems and child modules the product needs.
Governance is part of the engine
Roles, access groups, permissions, approval stages, audit trails, and lifecycle state share one consistent foundation.
Built to be operated
Caching, diagnostics, migration orchestration, request tracing, logs, and health tooling support the full system lifecycle.
Composable platform
The shared capabilities products should not have to reinvent.
Eleven versioned ecosystems form Evo's mandatory baseline. Child products add their own domain model without redefining the foundation beneath it.
Core
Identity, access, governance, lifecycle, navigation, and audit foundations.
Attachments
Secure file metadata, storage, variants, and content ownership.
Notifications
Channels, preferences, templates, targets, and delivery tracking.
Finance
Accounts, invoices, payments, receipts, settlements, and refunds.
Content
Reusable content counters and engagement projections.
Location
Regions, districts, and reusable place structures.
Forum
Boards, topics, posts, subscriptions, moderation, and reactions.
News
Categories, articles, locations, and public conversation.
Reporting
Datasets, templates, schedules, dashboards, exports, and delivery.
Transactions
Exact movement records, allocations, reversals, locks, and snapshots.
Subscriptions
Consent-aware campaigns, subscriptions, delivery outbox, and events.
Built with Evo
Explore all projects
Different missions. One dependable engine.
Evo already shapes products across faith, music, health, personal finance, project operations, and community work.
Browser utilities
Evo Tools
A collection of everyday browser tools for calculations, conversions, QR codes and more.
Complete View project
Web & mobile app
KibubuPesa
A personal finance platform and app for managing money accounts, transactions, budgets, debts and cash flow.
Complete View project
Church management
MenejaKanisa
A church management system that brings administration and financial records together.
Complete View project
Music platform
MuzikiHub
A platform for discovering and sharing music, connecting composers and supporting musical collaborations.
Complete View project
Communications
Mawasiliano
A platform for the Zanzibar Central SDA Church communications department, including volunteer applications.
Complete View project
School website
Z.A.A
The Zanzibar Adventist Academy website, presenting its nursery and primary programmes, admissions and school life.
Complete View projectA lifecycle the whole product can follow.
Evo keeps product rules, access, data shape, interface, and operations connected instead of treating them as separate afterthoughts.
-
01
Model the domain
Define the real entities, relationships, lifecycle, and ownership boundaries.
-
02
Govern the action
Attach permissions, actor scope, approval policy, state, and audit meaning.
-
03
Compose the experience
Build public, member, admin, and API surfaces from the same contracts.
-
04
Operate with evidence
Trace requests, inspect health, evolve sources, and verify every release.
The way Evo works
The quiet rules underneath every visible feature.
Fail closed
Authorization, scoped identity, hostile-input validation, and governed actions live below the interface.
Local language, first class
Swahili and English are part of the same interface contract, together with responsive light and dark themes.
Source-owned data evolution
Schema, views, seeds, and child overlays follow explicit ownership and dependency-aware composition.
Traceable by default
Requests, state changes, audit actors, cache behavior, and operational signals leave an inspectable trail.
Explore the family
See what one shared engine can become.
Explore the project gallery and the shared capabilities behind Evo products.