Browzer
Browser automation and scraping workspace.
A private cloud that Salik Qazi runs on hardware in his own home: identity, media, music software and the orchestration underneath. Nothing rented:
Every card is a real application capture. Music is open now; every protected lane stays off air until its Docker and browser smoke suite passes.
Browser automation and scraping workspace.
Synthetic observability prepared for an isolated demo dashboard.
Generated aviation, weather and geospatial observations on one map.
The automation workflow control room.
AI-assisted development inside the Lab.
A disposable shell prepared with a fixture-only home directory.
A fixture workspace prepared for the browser editor.
A sanitized television viewer prepared with sample stations.
A sanitized replica of the television management plane.
Stem splitting, transcription and AI-assisted music work.
SQ-11 TUNE IN ↗ Original tools for writing and producing music with less friction.
SSH prepared for the same fixture-only disposable shell.
A fixture launcher with generated workspace and health states.
A sanitized identity-directory replica with sample policies.
A single-sign-on layer sits in front of every service in the lab (the streaming network, the music tools, the admin surfaces), so there's one identity to manage and one door to lock, not a scattered pile of separate logins.
It's the same instinct that runs through the automation work: the boring, correct plumbing that everything else depends on gets built once and built right.
Underneath is a genuine streaming platform: an IPTV and media network Salik built and runs for family, not a hobby project pretending to be one.
It watches its own signal: each channel is health-sensed continuously, catching a feed that's degraded or gone dark before anyone watching notices. It behaves like real broadcast infrastructure because that's what it's built to be.
The lab also builds the tools it needs rather than buying them: ApproachableMusic, "Music Made Easy", is original software for writing and producing music with less friction, paired with an AI studio for the parts of that workflow worth automating.
Holding all of it together is a container orchestrator Salik wrote himself, provisioning and managing every service the lab runs: the same self-hosted, own-your-stack approach applied at the infrastructure layer.