Press Release: CyberEco Data Layer¶
FOR IMMEDIATE RELEASE
CyberEco Launches Open Data Layer for Human-Centered App Ecosystem¶
Four modular packages give developers a production-ready foundation for building privacy-respecting, storage-agnostic applications
February 2025 — Today, CyberEco announces the release of its data layer as four independent npm packages: @cyber-eco/types, @cyber-eco/firebase, @cyber-eco/auth, and @cyber-eco/services. Together, they provide a composable, storage-agnostic data infrastructure for building interconnected applications that respect user privacy and data sovereignty.
The Problem¶
Building interconnected apps that share identity, permissions, and data requires solving the same infrastructure problems repeatedly. Developers spend months on authentication, caching, permission systems, and data synchronization before writing a single line of business logic. Worse, most solutions create permanent vendor lock-in to a specific database technology.
As digital ecosystems grow, these problems compound. Each new app duplicates boilerplate, introduces subtle inconsistencies in permission logic, and deepens the dependency on infrastructure decisions made years earlier. Migration to new technologies becomes prohibitively expensive.
The Solution¶
CyberEco's data layer addresses these challenges with four principles:
Storage Agnosticism. The StorageAdapter interface decouples all business logic from any specific database. Services are written once against the interface; the concrete implementation (Firebase today, IPFS or blockchain tomorrow) is injected at runtime. An entire ecosystem's storage backend can be swapped without changing a single domain service.
Orchestrated Operations. The DataLayerService orchestrator handles the permission-check -> cache-lookup -> database-fetch -> cache-update -> real-time-sync -> webhook-emit pipeline in a single call. Developers focus on business logic, not infrastructure plumbing.
Privacy by Architecture. A 4-tier permission model (owner/admin/moderator/member) with conditional access constraints (time-based, IP-restricted, MFA-required) evaluates on every read and write. Permissions are enforced at the data layer, not bolted on at the application layer.
Production-Ready Performance. A multi-level cache with LRU eviction and per-collection TTL strategies reduces database reads significantly. Real-time sync broadcasts changes to all subscribers. Batch operations minimize round trips.
Getting Started¶
import { createDataLayer } from '@cyber-eco/services';
import { FirebaseStorageAdapter } from '@cyber-eco/firebase';
const dataLayer = createDataLayer({
adapter: new FirebaseStorageAdapter(() => getHubFirestore()),
cache: { strategy: { staleWhileRevalidate: true } },
sync: { enabled: true },
});
// Full data layer access in 5 lines
const profile = await dataLayer.sharedData.getSharedUserProfile('user123', 'requester');
const hasAccess = await dataLayer.permissions.hasAppAccess('user123', 'justsplit');
const expenses = await dataLayer.sharedData.getUserTransactions('user123', { appId: 'justsplit' });
What Developers Are Saying¶
"Before the data layer packages, adding a new app to CyberEco meant copying hundreds of lines of Firestore boilerplate, re-implementing auth checks, and hoping the permission logic matched the Hub. Now it's a single
createDataLayer()call and we're building features in minutes, not days."
Package Overview¶
| Package | Purpose | Dependencies |
|---|---|---|
@cyber-eco/types |
TypeScript interfaces and constants | None (zero runtime deps) |
@cyber-eco/firebase |
Firebase StorageAdapter implementation | Peer: firebase |
@cyber-eco/auth |
Authentication, SSO, permissions, JWT, 2FA | Peer: firebase, react (optional) |
@cyber-eco/services |
DataLayerService orchestrator + domain services | Only @cyber-eco/types + @cyber-eco/auth |
Frequently Asked Questions¶
Q: Do I need Firebase to use these packages?
A: Only @cyber-eco/firebase requires Firebase. The @cyber-eco/services package works with any StorageAdapter implementation. You could use Firebase, a mock adapter for testing, or build your own adapter for PostgreSQL, MongoDB, or IPFS.
Q: Can I use just the types?
A: Yes. @cyber-eco/types has zero runtime dependencies. Install it alone for type-safe data models.
Q: Is this production-ready? A: The underlying domain services have been running in the CyberEco Hub and JustSplit applications since 2024. The modularization adds orchestration abstractions on top of battle-tested code.
Q: How do I contribute? A: The packages are open source. Contributions are welcome — from new StorageAdapter implementations to additional domain services to documentation improvements.
About CyberEco¶
CyberEco is a human-centered digital ecosystem for conscious, connected, and sustainable living. We build modular applications that enhance financial collaboration, community engagement, and social connectivity — with user sovereignty and wellbeing at the core of every design decision.
Learn more at cybere.co
Contact: info@cybere.co