It's alsmot the end of May now and usually I’d make a joke about how the year is flying by, but honestly, the last four months have felt like a decade. Between stepping into the CEO role at NodeByte, shipping major updates for Emberly and ByteSend, and trying to keep my sanity intact through a truly unreasonable amount of coffee, it’s been a gauntlet.
I wanted to start doing these "periodic reviews" every 4 or 5 months to document what it actually looks like to build and lead in the current tech climate. Spoiler: It’s chaotic, it’s fast, and "simple" is officially dead.
The Transition: From COO to CEO
At the start of the year, I officially moved from COO and Lead Dev to the CEO role at NodeByte. While I’ve always been deep in the strategy and the code, shifting from "Operations" to "The Buck Stops Here" changes the perspective.
The biggest challenge isn’t the workload it’s the context switching. I’m still the Lead Developer at heart, but now I’m balancing high-level growth strategy for our platforms with the legal and corporate responsibilities of a CEO. I still spend my nights in the IDE (I refuse to be a CEO who doesn't know how his own stack works), but my days are now spent ensuring NodeByte is positioned to survive a landscape that is changing faster than ever.
The Q1 Shipping Log: Platform Maturity & Infrastructure Autonomy
The start of 2026 was defined by one goal: total infrastructure autonomy. Between January and May, we pushed two massive version jumps for our core platforms.
Emberly v2.4.2: The "Bucket Partners" Rollout
We closed out April by pushing Emberly v2.4.2, one of the most technically dense updates we’ve ever released. We’ve fully automated the storage pipeline:
- Auto-Provisioning: When a user buys a storage-bucket subscription, the system now auto-provisions a dedicated bucket, sets up Cloudflare DNS CNAMEs, and hooks up the lifecycle events with zero manual intervention.
- Tiered Storage: We’ve moved beyond a one size fits all model, supporting five distinct tiers (Standard to Accelerated) with region-specific selection and a redesigned UI.
- User API Keys: We killed legacy tokens in favor of a robust
ebk_prefixed system with SHA-256 hashing and usage tracking.
ByteSend v0.2.6: The "Custom Contract" Era
While Emberly was getting a storage overhaul, ByteSend was evolving into a pro-grade delivery engine. Just this week, we hit v0.2.6, which moves us away from rigid tiers and toward a flexible, contract based model.
- Slider-Based Billing: We replaced static plan cards with an interactive contract selector. Teams can now slide their marketing and transactional limits from 1k to 3M emails, and the system generates a custom Stripe checkout session on the fly.
- Unified Audit Trails: We introduced a first-class
/logsdashboard that merges email events, webhooks, and delivery logs into a single searchable audit trail. - Developer SDKs: I’m officially maintaining the initial Go SDK, joining our JS and Python surfaces to make ByteSend as easy to integrate as it is to self-host.
- Multi-Provider Notifications: Teams can now pipe system alerts (hard bounces, spam complaints, etc.) directly into Discord, Slack, Teams, or Telegram.
The Nexium Merge
We also successfully folded Nexium into the Emberly ecosystem. It was a massive architectural migration moving a live platform's heart into another while the patient was running but the consolidation has already halved our maintenance overhead.
The 2026 Security Debrief: Hardening the Fleet
If 2025 was about "AI hype," 2026 is about "AI consequences." We’ve officially entered the era of machine-speed exploitation.
- The AI-Auth Zero-Day (May 2026): We just saw the first confirmed case of an AI-developed zero-day bypassing 2FA on open-source admin tools. This is exactly why I’ve been pouring hours into my Cadence project—we need to detect synthetic footprints before they reach production.
- The Stryker Attack (March 2026): Seeing the medical tech sector hit with "wipe-style" attacks rather than just standard ransomware was a grim reminder that "backups" aren't enough. You need immutable infrastructure.
Enforcing Zero-Trust
Because of these shifts, we aren't just talking about security; we’re enforcing it. We are now officially moving to a strict Zero-Trust architecture across NodeByte, Emberly, and ByteSend.
This means no more "implicit trust" just because you're on a VPN or a specific IP. Every request, every access attempt, and every service-to-service communication across our entire fleet is now verified, authenticated, and encrypted. Whether it's a file transfer on ByteSend or a core API call on Emberly, if it isn't authorized at the point of entry, it doesn't happen. It’s a "hard-shell, hard-core" approach, but in 2026, it's the only way to sleep at night.
Homelabbing & Community
When I need to unplug from the "CEO brain," I go back to the basics: FiveM and RedM.
Working on FivePRS and general server scripting (Lua/C#) keeps me grounded. It’s a different kind of problem solving highly visual and completely separate from the SaaS world. Plus, the Pterodactyl and VirtFusion setups in the lab have been getting some much needed upgrades. You haven't lived until you've debugged a kernel panic while your dog a very confused black and white pitbull stares at you like you've lost your mind.
State of the Tech: My Hot Takes
- Cloud 3.0 is Self-Hosted: The "Cloud Tax" is becoming unbearable for startups. I’m seeing a massive migration back to hybrid and sovereign infrastructure. If you don't own the hardware, you're just renting your future.
- The "AI Agent" Reality Check: 90% of "agents" are just fancy if/else statements. The 10% that actually work are changing the industry, but the governance side is still a total Wild West.
- The Death of "Simple": Security and compliance have made the baseline "entry fee" for a tech product ten times higher than it was three years ago. There is no such thing as a "simple" web app anymore.
Vitals Check:
- Next Milestone: Clovr Launch (June 1).
- Coffee Level: Dangerous.
- Vibe: Focused. Tired. Ready to ship.
See you in 4 months for the next review.