I build the stuff I actually want to use myself.
My own programming language, my own hosting, my own Minecraft cloud, and research on a bio-neural AI architecture. All self-built, all self-hosted.
What's taking shape
No showcase filler — these are the projects I actively build and run.
BlueNet-Hosting
My hosting company. Game servers, web space and infrastructure — run on my own hardware with my own panel stack.
- Game servers
- Web space
- Own hardware
- Own panel
KryoCloud
My own Minecraft cloud. Node system, dynamic server groups and templates — built for networks of any size.
- Node system
- Server groups
- Templates
Kryonox
My Minecraft network. Own plugins, own systems, running entirely on KryoCloud.
- Own plugins
- Runs on KryoCloud
BIONIC in the cloud
Access to BIONIC, hosted on BlueNet. Currently being built.
Go to loginWhat I work with
The stack I build with day to day — from the language all the way down to the infrastructure.
Emerald
My own LLVM-based language — compiled to native binaries for every OS that LLVM supports, at speeds from close to C up to C level. And the compiler doesn't minimize RAM via a GC: it eliminates it. As much as possible goes into CPU registers, the rest is sorted into six tiers.
public class FlowPoint {
private Int x;
private Int y;
public FlowPoint(Int x, Int y) {
this.x = x;
this.y = y;
}
public Int sum() {
return this.x + this.y;
}
}
main() {
FlowPoint point = FlowPoint(10, 20);→ folded
Int total = point.sum();→ folded
String label = "sum: " + total.toString();→ inline
println(label);
} BIONIC
Bio-Inspired Organic Network for Intelligent Computing
My own bio-neural AI architecture — and currently the only one that runs on CPU and RAM alone, with solid performance. No GPU cluster, no token sampling, no brute force.
BIONIC doesn't work with tokens and probabilities, but with states. Per request only the neurons needed for the best possible answer activate — the rest of the net stays silent. That way the network understands concepts instead of just guessing the next most likely continuation.
The first test AIs already ran through successfully. Right now BIONIC is written in Crystal — the port to Emerald is the next step, so architecture and language come from one hand.
Sparse Activation
Only relevant entry points fire, the rest of the net stays fully inactive. Compute scales with the active structure — not with the total size of the knowledge.
Event-Driven
Processing runs event-driven over prioritized signals, hard-capped by activation budget, spread depth and time limit. Every thinking cycle stays deterministically bounded.
Persistent State
No empty context per request. Topics, memories, relationships and internal modulators stay part of the active network structure across interactions.
Organic Memory
Memory as connected semantic structures with entities, causality and weighting — associative recall by meaning instead of plain text similarity.
Excitation & Inhibition
Excitatory and inhibitory signals compete. Decisions emerge from controlled competition, not just from the strongest activation.
Adaptive Learning
Local plasticity instead of global retraining: strengthen paths, cut unreliable connections, consolidate recurring patterns — at runtime.
Dynamic Clustering
Related units group dynamically into clusters that activate, merge, split or fade in relevance when unused.
Internal Modulation
Modulators like attention, uncertainty, urgency or confidence steer which structures fire and how long a thinking cycle runs.
- 1 Input signals are translated into internal stimuli.
- 2 Relevant entry units and clusters are activated.
- 3 Activity spreads across weighted connections.
- 4 Inhibitory and modulating signals constrain and prioritize.
- 5 Relevant memories and states enter working memory.
- 6 Multiple interpretations and responses compete.
- 7 A stable internal state or decision emerges.
- 8 The result is handed to the action, language or control layer.
- 9 Successful or faulty paths are adjusted locally.
- 10 The updated state persists into the next cycle.
BIONIC, ready to use
The AI Cloud is the way into BIONIC — hosted on my own infrastructure at BlueNet-Hosting. It is currently being built.
-
Runs on CPU & RAM
No GPU farm behind it. BIONIC only needs regular server hardware.
-
State persists
No empty context per request. Topics and memories stay active across interactions.
-
Self-hosted
Runs on BlueNet hardware, not at a big cloud provider.
Everything interlocks
The projects aren't a loose portfolio — each one builds on the others.
- 1
BlueNet-Hosting provides the hardware
Own servers, own network, own panel — the base everything else runs on.
- 2
KryoCloud orchestrates the servers
The node system distributes and scales Minecraft servers across the BlueNet infrastructure.
- 3
Kryonox runs on KryoCloud
The network is the real-world test of the cloud — with its own plugins and systems.
- 4
Emerald becomes the foundation
BIONIC is ported from Crystal to Emerald — own architecture on own language.