Paludarium Project

Choose where you want to enter the project

Your Slice of a Living Rainforest in the Making

This project is built around a future 24/7 livestream from a handcrafted A paludarium is a slice of rainforest in glass: terrarium above, aquarium below. , created to bring the feeling of a tropical rainforest into everyday life. It is meant as a place you can return to whenever you need a calmer moment, a fresh focus, or simple wonder. Behind that atmosphere is a real process: careful design choices, practical build steps, and transparent project decisions that shape the ecosystem over time. As you continue, you can follow the path that matches your curiosity and discover the project from different angles, from immersive mood to deeper system insight.

Now: You can explore the first project structure, public baseline, and channel pathways. Next: Launching the first YouTube videos to showcase the project and document its build progress.

Illustration of a blue poison dart frog on a dew-covered leaf in a sunlit rainforest

The Experience

The Nature Experience

Immersion & Observation

Step away from the noise. I am building this ecosystem from an empty glass enclosure, slowly enough to let each layer become stable before animals enter. The aim is a calm, cinematic 24/7 view of a living rainforest, but animal welfare sets the pace.

 Illustration of a microchip on a golden circuit board surrounded by workbench tools

The Blueprint

The Engineering Blueprint

Architecture & Automation

Behind the calm scene is an engineering problem: climate, water, power, sensors, and automation all have to work together. I document what I build, what I test, what fails, and what the measurements actually show.

 Illustration of a camera, microphone, and coffee mug on a desk by a plant-filled window

The Operator

The Person Behind MPBMy Private Little Biotope

Decisions · Gear · Real-Life Balance

I explain the principles behind my decisions, show the production setup I actually use, and share how I keep MPB moving alongside a full-time job while making room for fitness and recovery. It is to show the real choices, limits, and responsibility behind the build.

Public build journal

Weekly Build Notes

A curated overview of how the project becomes more real, stable, and understandable over time.

Week 33 / The First Real Footage

The First Test Footage Meets Real-World Conditions

  • The first real test footage for the opening video was actually recorded and looked at — the first time the plan met everyday conditions instead of a checklist. The early signs are encouraging: the picture holds up and the spoken words come through clearly.
  • But recording something is not the same as approving it. A second, independent review confirmed the main impressions, while the final technical sign-off stays deliberately open and waits for a proper look on a calibrated screen. That part is still running, so what counts today is a promising starting point rather than a finished result.
  • The first scene to be filmed on location was planned as a calm, fixed shot instead of a moving one — a short, quiet moment right before the build begins. It is a small example of how the project would rather get one controlled take right than chase something rushed.

Week 32 / One Place To See Everything

The Project Gets Its Own Control Room

  • Everything the project has to keep track of now sits in one place: the work that is planned, the risks that are known, the workflow behind the first video, and the sketches that explain how the pieces fit together. Until now each of those lived in its own document and only made sense one at a time.
  • With that came a stricter rule about safeguards: putting a measure in place no longer counts as finished. It stays open until there is evidence that it actually works. On that basis every safety and risk measure carried over from the early planning was reviewed one by one — and where proof was missing, the gap stays visible instead of being quietly closed.
  • The camera work from last week carried on, and that part is still running: several recording profiles are saved and confirmed to survive a restart, while the rest are still being checked. None of this shows up on screen, but it decides whether the first video rests on settled ground or on guesswork.

Week 31 / From Script To Camera

The Script Is Finished And The Cameras Come Out

  • The script for the first video reached its finished shape — a complete run from the opening scene through planning, temperature tests, the build itself, and the wiring, to the moment the rack stands in place.
  • Then the equipment came off the shelf, and that part is still running. Cameras, microphones, stabiliser, and lights are being worked through one combination at a time; the shared recording standard both cameras will use is settled, while the detailed setup and the real-world tests continue. Every setting that proves itself is written down rather than rediscovered later.
  • For visitors this is the slow, unglamorous half of making a video, and it is where a project shows its habits: original recordings kept untouched, a verified second copy of anything worth keeping, and a rehearsal before the shots that could never be taken again. What you will eventually hear is a real voice, with subtitles where they help — no synthetic narration.

Week 30 / The First Video Takes Shape

Planning Turns Into A Real First Video

  • The first video became actual work: the build of a custom, living-room-friendly rack for the machines that run the project, now with an approved concept, a planned length, and a production plan behind it.
  • The route from idea to finished video was settled along the way — a repeatable sequence with clear checkpoints, an honest early look at whether a topic can carry a video at all, and the decision that every longer video gets a companion page here for the detail that does not fit on screen.
  • For visitors this is where the build starts moving from written notes towards something to watch. There is no promised release date; the video appears once the rack is built and the footage holds up.

Week 29 / Evidence Before Assumptions

A Wrong Diagnosis Becomes A Better Build

  • Follow-up testing overturned the original diagnosis: the small computer itself was sound, and an incompatible memory module had caused the strange failures.
  • With a supported module installed, the machine passed its memory, load, restart, and temperature checks and is now prepared for its future role beside the habitat.
  • A wider quality review also sharpened the website, media workflow, and operating safeguards, so the next public release rests on clearer decisions rather than assumptions.

Week 28 / Earning Trust

The Build Earns Its Trust The Hard Way

  • A brand-new computer meant to run the habitat started misbehaving in strange, on-and-off ways, so an AI assistant and I chased the symptoms down step by step until we had the culprit — the board itself, not the parts around it. It's gone back for a replacement, because nothing goes into service near living animals until it has earned that trust.
  • For the first time, the project looked at how the live site is actually being used, drawing only on privacy-friendly server records — no tracking scripts, no cookies, and no consent banner needed.
  • It also quietly tightened its own inner structure and safeguards, staying true to a simple habit: measure what is real, respect the visitor's privacy, and build in careful, controlled steps.

Week 27 / Reviewed And Refined

The Public Site Gets A Thorough Quality Pass

  • The whole public website went through a thorough, independent review — how fast it loads, how accessible it is, how easily it is found, and how it reads — turning a general sense of "good enough" into a clear, prioritized list of concrete improvements.
  • The first of those improvements were applied right away: easier keyboard navigation, larger touch targets on phones, lighter and faster images, cleaner legal text, and a leaner set of pages that feel like one coherent home.
  • For visitors, the site becomes smoother and more comfortable to use on any device, while keeping its steady signal: careful, measured work rather than rushed launches.

Week 26 / Resilient By Design

The Control Side Is Built To Keep Itself Running

  • The control side of the first habitat moved onto its own dedicated, silent, always-on mini-computer, kept separate from the central setup.
  • The build also gained a clear plan for what should happen if individual parts go offline, so the habitat's basic conditions can be held locally instead of depending on one central system staying up.
  • For anyone following along, this is steady, careful engineering: a setup designed for calm reliability well before the habitat goes live.

Week 25 / Honest And Measured

The Site Gets Leaner While The Build Keeps Measuring

  • The Operator section was streamlined: the camera, audio, and editing setup now appears as one compact, honest overview instead of a separate page.
  • Behind the scenes, the project decided how it will keep an eye on power use for its setup and mapped out which climate conditions it will track once the habitat is alive.
  • For visitors, this continues a calm pattern: fewer empty promises, more visible structure, and real measurement planned before anything goes live.

Week 24 / From Planning To Measuring

The Project Starts Measuring The Real Environment

  • The wireless conditions around the future habitat were measured directly over several days, turning a planning assumption into real data.
  • The video and stream production workflow gained a shared visual model, and the project's planning backbone became more consistent.
  • For visitors, this shows a calm, evidence-based approach: decisions are prepared with real measurements instead of guesswork.

Week 23 / Infrastructure Becomes Tangible

The Hidden Backbone Starts Becoming Real

  • Core machines and local network foundations moved from plan into verified setup.
  • The build now has clearer roles for media, runtime, storage, and future control.
  • For visitors, this makes the future rainforest stream feel credible instead of purely aspirational.

Week 22 / Runtime Map

The Home Infrastructure Plan Gets A Route

  • The home infrastructure review became a concrete migration path.
  • Network, media, stream, and safety responsibilities were separated before live operation.
  • The takeaway is simple: the calm scene will be supported by serious engineering.

Week 21 / Media Workflow

The Future Stream And Videos Get A Clearer Shape

  • The video and livestream workflow was organized into clearer production, strategy, and operating layers.
  • Risk, documentation, and handover rules became more deliberate.
  • Future updates can now point to real parts of the system instead of vague behind-the-scenes work.

Week 20 / Creator System

The Project Starts Becoming A Repeatable Story

  • YouTube and post-production planning were consolidated into a cleaner creator workflow.
  • Editing tools, channel logic, and the website role were connected into one content path.
  • That helps the project grow as a series, not just as occasional updates.

Week 12 / Release Hygiene

The Site Gets Quieter, Safer, And Easier To Maintain

  • The website went through release, cache, security, and documentation cleanup.
  • Publishing rules and technical checks became part of the normal workflow.
  • This quiet work helps visitors land on a site that feels stable, current, and carefully maintained.

Week 11 / Operator And MVP Clarity

The Website Becomes A Coherent Homebase

  • The website stories, tests, and operator perspective were aligned with the real project.
  • The pages became less like placeholders and more like a shared home for the build.
  • Visitors get clearer routes into nature, engineering, and the human work behind both.

Week 10 / Blueprint Shape

The Engineering Side Gets Its Public Frame

  • The Blueprint area gained a structure for architecture, automation, monitoring, and build references.
  • Visual cards made the technical side approachable without pretending the full archive is ready.
  • The site started showing how the system will be explained, not only that it will exist.

Week 8 / Public Safeguards

The Website Gets The Small Details Right

  • Privacy, security, legal access, and the Experience page were strengthened.
  • The live site became more reliable around navigation, cache behavior, and basic public safeguards.
  • These details are mostly invisible, but they make the project safer and more dependable for visitors.

Week 7 / Website Foundation

The Project Becomes A Website System

  • The project moved from planning artifacts into a real website foundation.
  • Landing structure, cluster paths, legal pages, tests, and a publishing workflow took shape.
  • The first public frame stayed intentionally lean so future updates can grow from real progress.

Choose Where You Want to Follow

YouTube

Long Videos, Shorts & the Future Livestream

YouTube will become the main video home of My Private Little Biotope: longer build stories, shorter observations, and later the 24/7 paludarium livestream. If you want to see how I build the system and why I make certain decisions, this is the main channel to follow.

Open YouTube

Instagram

The Visual Gallery: Curated Stills & Atmosphere

Instagram is the quieter visual side of the project: selected stills, close details, and carefully framed moments as the paludarium takes shape. Follow there if you prefer the build through images rather than long explanations.

Open Instagram

TikTok

The Pulse: Quick Impressions & Motion

TikTok is planned for short build moments, movement, and small observations that do not need a long explanation. It is the quickest view of the project, without pretending that every update is a major event.

Open TikTok

X

The Operator’s Log: Real-Time Updates & Thoughts

X is the shortest written path to the project. I use it for work-in-progress notes, quick observations, and brief thoughts about the technical and everyday decisions behind the build.

Open X