A creative technology collective building modular software systems,
experimental infrastructure, and runtime platforms.
Modular Content develops independent but interoperable software systems built around modular architecture principles.
The organization focuses on designing infrastructure and runtime environments where systems remain:
- composable
- observable
- deterministic
- independently operable
Projects are treated as building blocks of a larger technical ecosystem, where services can evolve independently while maintaining clear architectural boundaries.
Event relay and webhook delivery infrastructure
ModRelay is a lightweight service that allows systems to create relay endpoints that forward events to external services with reliability and control.
Core capabilities include:
- route isolation
- rate limiting
- retry delivery logic
- delivery logging
- optional HMAC verification
- replaying failed events
The system acts as a reliable event routing layer between services and external integrations.
Website
https://modularcontent.dev/modrelay
Runtime framework and ecosystem for Garry's Mod
ModularWork defines a structured runtime environment for building independent game schemas and services.
Unlike traditional gamemodes or addons, it establishes a system architecture based on strict design principles.
Key architectural ideas include:
- a centralized Game Coordinator acting as the source of truth
- deterministic system behavior
- schema-based gameplay composition
- runtime independence from external services
- strict separation between core systems and schemas
This architecture enables scalable multi-server environments and controlled system evolution.
Website
https://modularcontent.dev/modularwork
Modular Content projects follow a shared architectural philosophy.
Systems should be:
Modular
Each component should exist as an independent unit.
Deterministic
Behavior must be predictable and explainable.
Observable
It must always be possible to understand system state and dependencies.
Resilient
Failure of external services should degrade functionality rather than terminate systems.
This philosophy allows projects to evolve independently while remaining interoperable within a larger ecosystem.
Documentation and ecosystem resources are maintained separately from core projects.
Wiki
https://wiki.modularcontent.dev
Architecture documentation, development notes, and internal system references.
Forum
https://forum.modularcontent.dev
Community discussions, development logs, and ecosystem topics.
For inquiries related to the organization:
Administration
admin@modularcontent.dev
Support
support@modularcontent.dev
Legal
legal@modularcontent.dev
Security reports
security@modularcontent.dev
