Hi everyone ๐
I'm working on a project called WOS (Workspace OS), which actually started as my vocational final project. It was born out of my own frustration with how software systems connect with one another today.
We often hear that systems are "integrated," but in practice, it often feels superficial. We end up writing repetitive boilerplate code, dealing with messy spaghetti architectures, and relying on rigid, hardcoded connections. Even when trying to connect AI agents or cross-platform services, they struggle behind the scenes because the underlying infrastructure wasn't designed for seamless interaction from the start.
Instead of writing custom glue code over and over, I tried stepping back to build a lightweight, config-driven middleware core. The idea is to act as an adapter layer that allows services and tools to communicate through a single unified protocol without hardcoding each connection.
๐ฏ What I'd love to validate
Since I'm building this from my own perspective, I'd really love to validate my assumptions with experienced system engineers and developers here:
The Pain Point: Is this integration friction something you actually face in production or self-hosted setups, or are there existing solutions handling this better that I might have missed?
The Architecture: Looking at this core concept, where do you see potential bottlenecks, security risks, or architectural flaws?
Missing Features: What essential primitives or adapters are needed to make a core like this useful for real-world stacks?
๐ฌ Let's discuss
I've opened the source code and design documentation on GitHub because I don't believe fundamental system architecture should be built or owned in isolationโit grows best when refined by the developer community.
GitHub Repository: https://github.com/Auto55597/wos
GitHub Discussions: https://github.com/Auto55597/wos/discussions/2
Any feedback, constructive critique, or thoughts are deeply appreciated. Let me know what you think in the comments below!
Top comments (0)