Hands-on experience with AI, self-hosting, Linux, and the developer tools I actually use

Latest

Hands-on experience with AI, self-hosting, Linux, and the developer tools I actually use

Three differently sized water reservoirs piping into a single server rack, illustrating SQLite, MariaDB, and PostgreSQL scaling ceilings.

Self-Hosted Databases in 2026: Postgres vs SQLite vs MariaDB

Picking a self-hosted database in 2026 comes down to one question: when does it force you to migrate? SQLite holds until about one write-heavy app server (~10 GB, single writer). PostgreSQL 18 is the default that almost never makes you move. MariaDB 12.3 LTS earns its spot mainly when you already live in the MySQL world.

Key Takeaways

  • SQLite serializes writes, so one busy app server is its real ceiling.
  • Postgres 18 is the default that almost never makes you migrate later.
  • MariaDB fits best when you already run MySQL tooling.
  • SQLite runs with no daemon and almost no RAM, while Postgres needs tuning.
  • The SQLite to Postgres jump is a planned move, not an emergency.

What are the best self-hosted databases for web apps in 2026?

For a self-hosted web app, three engines cover almost every case: PostgreSQL is the do-everything default, SQLite is the embedded single-file engine, and MariaDB is the MySQL-compatible community fork. All three are open source and free to run on your own box.

Five ESP32 chip modules on a grid, each emitting a colored radio halo, with a battery and a gauge needle pointing from milliamps down to microamps.

ESP32 Boards for ESPHome: Radio-First Picks, Deep-Sleep Tested

The best ESP32 board for ESPHome in 2026 is the one whose radio matches the job, then the one whose deep-sleep current matches your power source. Pick the ESP32-C6 for Matter-over-Thread, the ESP32-H2 for battery Zigbee, and the classic ESP32 or S3 for mains BLE proxies. Bare modules sip 7-10 microamps asleep, but stock dev boards waste 5-15 mA.

Key Takeaways

  • Match the chip to the radio first: C6 for Thread, H2 for Zigbee, S3 for BLE proxies.
  • Bare ESP32 modules sip 7-10 microamps asleep; stock dev boards waste 5-15 mA.
  • The C6 is the only ESP32 with Wi-Fi 6 plus a Thread radio, great for Matter.
  • The H2 has no Wi-Fi, so it lives or dies on a Zigbee or Thread mesh.
  • All five chips work in ESPHome, but C6 and H2 need the ESP-IDF framework.

What is the best ESP32 board for ESPHome in 2026?

There is no single winner, because the right board depends on the radio your project needs. So start from the radio, then filter by power source, then by GPIO and flash headroom. That order saves you from buying a powerful chip that lacks the one radio your sensor actually requires.

Cutaway house drawn as a Zigbee mesh with sensor nodes wired to a coordinator stick and a few older nodes dropping off

Sub-$20 Zigbee Sensors That Stay on the Home Assistant Mesh

For Home Assistant in 2026, the best sub-$20 Zigbee sensors are Sonoff’s SNZB line and Third Reality. Both pair cleanly with Zigbee2MQTT and ZHA, need no vendor hub, and stay on the mesh. Older Aqara and Xiaomi units cost less but drop off through cheap routers and lock settings you cannot change.

Key Takeaways

  • Sonoff SNZB sensors pair with Zigbee2MQTT and ZHA, no Sonoff hub needed.
  • Older Aqara and Xiaomi sensors often fall off the mesh through cheap routers.
  • The Aqara RTCGQ11LM motion sensor locks re-trigger at 60 seconds you cannot lower.
  • Coin-cell Sonoff sensors last 3 to 5 years; AAA sensors closer to one year.
  • The cheapest sticker price is rarely cheapest once you count battery swaps.

What are the best Zigbee sensors under $20 for Home Assistant?

Here is the curated shortlist by sensor type, with rough street prices and the battery each one uses. Every pick below pairs to Zigbee2MQTT or ZHA directly, so you do not need the maker’s own bridge.

Four radio-tower figures on a podium inside a cutaway house, with a cracked cloud icon severed above the local mesh

Zigbee vs Z-Wave vs Matter vs Thread: What Reddit Says in 2026

Reddit’s hands-on 2026 verdict on Zigbee, Z-Wave, Matter, and Thread diverges sharply from the spec-sheet consensus. The highest-upvoted owners rate Z-Wave the most reliable, call Zigbee 4.0’s new sub-GHz band a revival rather than a death, and report Matter-over-Thread as the least stable protocol they run. Here is each axis matched to the cohort that lives with it.

Key Takeaways

  • Reddit’s hands-on crowd rates Z-Wave the most reliable of the four in 2026.
  • Zigbee 4.0’s new sub-GHz band revived the “Z-Wave is dead” meme, but it needs a new controller.
  • Matter-over-Thread draws the most complaints, often fixed by moving to Thread channel 25.
  • Zigbee wins on price and device variety because it is an open standard.
  • All four run locally, so the failure redditors fear is the cloud, not the radio.

The Spec-Sheet Consensus vs What Reddit Actually Runs

The published 2026 story is tidy. Matter is the cross-ecosystem future, Thread is its low-power mesh, Zigbee is the aging incumbent, and Z-Wave is the niche old-timer. That narrative got fresh backing when Matter 1.5 shipped in November 2025 , adding cameras, closures, and energy device types, with a 1.5.1 maintenance update following in March 2026.

Four distinct robots in a sealed glass workshop, each cabled to one central llama-stamped engine, with an eight-link reliability gauge fading at the end.

Self-Hosted AI Agent Frameworks in 2026: Local-First Compared

A self-hosted AI agent needs to run entirely on your own Ollama or vLLM with no OpenAI key. All four major frameworks claim that support, but only LangGraph and CrewAI wire to a local model with zero workarounds. AutoGen needs a client swap, and Flowise needs one base-URL field. The model, not the framework, is the real reliability ceiling.

Key Takeaways

  • All four run on Ollama, but only LangGraph and CrewAI need zero workarounds.
  • The small local model, not the framework, is what breaks tool calling.
  • Flowise is the only true no-code pick; LangGraph is the most code-heavy.
  • Most framework docs still assume an OpenAI key, so budget setup time.
  • Use Qwen3 or larger for agents; smaller models drop tool calls under load.

Why Local-First Fitness Is the Axis That Counts

Most “best agent framework” roundups assume you have an OpenAI key and a credit card. The first code sample spins up a hosted client, and the “swap to local” path is a footnote if it shows up at all. Self-hosters ask a sharper question about whether any of these run on their own box with no cloud call.

Three roped climbers ascend a cliff whose contour lines form a topographic curve over stacked memory chips at the base.

Local Image Models in 2026: Qwen vs FLUX vs SDXL on VRAM

No single local image model wins everything in 2026. After running one prompt set on a single 24 GB GPU, the picture is clear: Qwen-Image renders legible in-image text, FLUX leads prompt adherence, and SDXL keeps the deepest LoRA library on the lowest VRAM. The real frontier is quality-per-VRAM, not one champion.

Key Takeaways

  • No local model wins on everything; pick the one that fits your bottleneck.
  • Qwen-Image renders legible in-image text far better than its rivals.
  • FLUX.2 leads prompt adherence but is the heaviest on VRAM.
  • SDXL still has the biggest LoRA and ControlNet library by far.
  • Check the license: FLUX dev blocks selling output, Qwen and SDXL don’t.

How Do I Choose a Local Image Model in 2026?

Match the model to the one thing you can’t compromise on. That single rule beats chasing a mythical “best” pick, because each model sits in a different corner of the quality-per-VRAM map. The 2026 local field narrows to three serious families, and the rest are mostly noise.