Service migration
Selected services moved from an SBC-centric start to a dedicated x86 server tier. The result is more headroom, cleaner failure domains and easier maintenance.
SERVICE CONSOLIDATIONAn independent home-server project and the open journal behind it — self-hosted tools, media, automation, a local AI lab and a Windows-98-era sleeper PC, built in small, verifiable steps.
A quick snapshot of what is active, evolving or still on the drawing board.
What changed during the latest development stretch: service migrations, recovery work, network redesign, workstation experiments and a growing local AI lab.
Selected services moved from an SBC-centric start to a dedicated x86 server tier. The result is more headroom, cleaner failure domains and easier maintenance.
SERVICE CONSOLIDATIONBackups are being treated as a recovery system, not just a copy job: inventories, integrity checks, restore notes and safer migration plans.
VERIFY, THEN TRUSTA dedicated firewall platform, private DNS design and IPv6-aware remote access are becoming the new network foundation.
FOUNDATION REWORKA workstation now runs Windows and Linux side by side, giving GPU-heavy local experiments a dedicated Linux environment without giving up the Windows side.
WINDOWS + LINUXLocal image models gained a browser interface and isolated per-model workers. The focus is reproducible experiments without depending on a cloud runtime.
LOCAL / ISOLATED WORKERSThe retro machine has moved beyond the planning stage: core hardware integration is under way, with boot validation and the remaining retro details next.
INTEGRATION PHASEThe website became part of the experiment: one HTML file, multilingual, interactive, source-linked and substantially faster to load.
ONE FILE / MANY LAYERSA symbolic map of the countries that have shaped the project through development, testing, culture and everyday use.
The name comes from Vojka, a village in Srem, Serbia. Its landscape has carried routes for centuries. That makes it a strangely perfect name for a project about networks, systems and things that keep moving.
Archaeological research documents a major west-east Roman road through the territory of modern Vojka. It connected Bassianae with Singidunum.
Brdašica is an Avar-period necropolis. A belt buckle from a Hunnic warrior was also found in the Vojka area during excavations in the 1960s.
Vojka is first mentioned in written records in 1416.
The village later became known for windmills, border guards and vineyards. The windmills are still remembered in the village coat of arms.
The name becomes VojkaOS. Roads become routes, relays become services and the backbone keeps going.
~1800 YEARS*
A joke, not an archaeological uptime SLA. The Roman-road layer is historical; the metric is playful.
Historical claims here are source-linked. The backbone metaphor, upgrade button and terminal jokes are ours.
Small modules with real jobs, connected by a privacy-first design.
Containers, storage, backups, private DNS, monitoring and the technical foundation.
OPEN DEV LOG →A playful system companion that turns health signals, backup results and network warnings into a small visual character.
/ \__ ( @\___ / O / (_____/ /_____/ UOPEN PROJECT →
A private multilingual app for food locations, expiry dates and reminders.
MULTILINGUAL / PRACTICALBackups are being treated as a recovery system, not just a copy job: inventories, integrity checks, restore notes and safer migration plans.
OPEN HEALTH →A cleaner media layer with verified sources, organised libraries, recovery in mind and carefully separated multi-user access.
OPEN PROJECT →A curated live-TV experience with EPG, channel health checks, direct channel navigation, favourites and separate user views.
OPEN PROJECT →A new encrypted path connects trusted remote clients to selected private services without opening inbound router ports.
OPEN NETWORK →Started in July 2026. The Windows-98-era shell is now in active hardware integration. Core components are moving into place; boot validation, fitment, retro I/O and finishing work come next. The goal stays the same: nostalgic outside, wildly overqualified inside.
BUILD STATUS: INTEGRATINGOPEN PROJECT →Local image models gained a browser interface and isolated per-model workers. The focus is reproducible experiments without depending on a cloud runtime.
ACTIVE / EXPERIMENTALOPEN DEV LOG →A planned private cloud for files, synchronisation, photos and selected sharing.
PLANNEDA demonstration of the health model: useful signals, verification and clear states instead of dashboard soup. The values are illustrative demo data.
The VojkaOS backup solution is custom-built to run the backup automatically, verify the result afterwards and only then report the outcome. If verification succeeds, WatchMila receives the good-news event. If something is wrong, the same path turns into a warning instead of silently pretending everything is fine.
During network configuration, an incorrect DNS value was entered on one network. WatchMila detected the resulting problem immediately and surfaced a warning, turning a small configuration mistake into a visible event instead of a quiet failure.
A playful system companion that turns health signals, backup results and network warnings into a small visual character.
A cleaner media layer with verified sources, organised libraries, recovery in mind and carefully separated multi-user access.
A curated live-TV experience with EPG, channel health checks, direct channel navigation, favourites and separate user views.
Started in July 2026. The Windows-98-era shell is now in active hardware integration. Core components are moving into place; boot validation, fitment, retro I/O and finishing work come next. The goal stays the same: nostalgic outside, wildly overqualified inside.
Milestones focus on what changed, what was learned and what comes next.
Backbone Edition: the site gained the Why Vojka story, sourced history, an interactive Roman-road-to-network visual, refreshed progress notes and a larger terminal toybox.
Selected services were migrated and consolidated onto a more capable x86 server tier, reducing dependence on a single small node.
Backup work expanded from “copy it somewhere” toward inventories, verification, restore notes and migration-aware recovery planning.
The network foundation moved toward a dedicated firewall platform, private DNS design and IPv6-aware remote connectivity.
A workstation gained a Linux dual-boot path for GPU-heavy local AI experiments while keeping its Windows environment.
The local AI lab grew into a browser-facing multi-model environment with isolated workers and reproducible model-specific launch paths.
The Sleeper PC moved into active hardware integration. The retro shell remains the joke; validation and finishing are the serious part.
Continue the network migration, harden recovery workflows, publish better project stories, expand monitoring and keep iterating.
Sleeper PC photos will be one of the first real project collections. The gallery stays folded until you want it.
A playful public terminal. It navigates and explains the project but has no access to a real server.
ping rome, traceroute singidunum or cat /etc/vojka/history.VojkaOS is where home servers, networks, local AI, automation, retro hardware and slightly unnecessary experiments end up living together.
VojkaOS is an independent personal project. It is not affiliated with, endorsed by, sponsored by or officially connected to any company, vendor, broadcaster, platform or organisation mentioned on this website.
References to products, services, software, brands or technologies describe tools used, tested or discussed by the project. They do not imply a collaboration, partnership, sponsorship or endorsement.
VojkaOS does not offer employment, freelance work, consulting, paid support, products, subscriptions or other commercial services. Nothing on this website is an offer to buy, sell, hire, contract or enter into a business relationship.
Product names, logos, trademarks and registered trademarks remain the property of their respective owners. Their appearance here is for identification and descriptive purposes only.
VojkaOS does not claim ownership of third-party media, broadcasts or other protected content. Rights remain with the respective owners and providers. Public project pages describe the technical system and its development, not ownership of third-party content.
The website is designed to work with minimal data collection. Any future feature that processes personal data should have a clear purpose, collect only what it needs and use appropriate protection.
This website is a public window into an ongoing personal technology project. Information may change as the project evolves and is provided for documentation and demonstration purposes.
The site stays intentionally lightweight: one file, minimal dependencies, clear project notes, source links where history matters and enough terminal nonsense to keep it fun.
The project name comes from a real place with a surprisingly deep infrastructure story. The sourced history and the intentionally ridiculous backbone analogy live on their own page.
OPEN WHY VOJKA →