Bun replaces four dev tools with one binary, plus three more worth your time
Bun is the one I keep coming back to. It's a runtime, a bundler, a test runner, and a package manager in a single binary, and it's faster than the Node tools it replaces at nearly every one of those jobs. The whole thing is free, no paid tier hiding the good parts. For a new project, there's almost no reason not to try it. The rest of this week leans the same direction: tools that let you own the thing instead of renting it. Plausible is a clean, privacy-first analytics dashboard you can self-host, no cookie banner, no handing your visitor data to Google. Cal.com does what Calendly does, scheduling links and calendar sync, except you can run the whole thing on your own server. And Lark's official CLI wraps 200+ commands across their suite, so if you live in Lark you can automate most of it from a terminal. None of these are new ideas. What changed is how good the open source versions got. A few years ago, self-hosting your analytics or your scheduling meant accepting a worse product to save money. That trade-off is mostly gone. Pick the tool because it's better, not because it's cheaper.
Fast JS runtime, bundler, test runner, and package manager
The Lens
Bun is a runtime, bundler, test runner, and package manager rolled into one binary. One install, one tool. It's written in Zig and JavaScriptCore (Safari's engine) instead of V8, and the speed difference is real. Installing packages is noticeably faster than npm or pnpm. The runtime starts faster than Node. The bundler is faster than esbuild in most benchmarks. The test runner is Jest-compatible but runs parallel by default. Everything is free. No paid tier, no cloud offering. The license is technically listed as 'Other' but Bun uses MIT for the core runtime, so you can use it commercially. Solo to large teams: free across the board. Drop it into any JS/TS project. It's Node-compatible enough that most packages work without changes. The catch: 'Node-compatible' isn't 'Node-identical.' Some npm packages that depend on native Node APIs or specific V8 behaviors will break. The ecosystem is still catching up: CI environments, hosting platforms, and tooling don't always support Bun natively yet. On a team with established Node infrastructure, migration has real costs. For new projects, it's a no-brainer to try.
A command-line tool for Lark/Feishu Open Platform, built for humans and AI Agents. Covers core business domains including Messenger, Docs, Base, Sheets, Calendar, Mail, Tasks, Meetings, and more, with 200+ commands and 19 AI Agent Skills.
The Lens
This official CLI covers everything. Messenger, Docs, Base, Sheets, Calendar, Mail, Tasks, Meetings, and more across 200+ commands with 19 pre-built AI Agent skills. The setup is fast: 3 steps from install to first API call, with one-click app creation and interactive login. Built in Go, MIT licensed. Every command has been tested with real AI agents, so the output formats and error handling are designed for machine consumption, not just human use. This is official from Lark Technologies, not a community wrapper. The catch: this is only useful if you're in the Lark/Feishu ecosystem. If your team uses Slack and Google Workspace, there's nothing here for you. And 'AI Agent acts under your identity' means the agent has your permissions. A hallucinating agent could send messages or modify documents as you. The security model requires careful scoping.
Lightweight privacy-friendly web analytics
The Lens
Plausible is a cookie-free analytics dashboard that fits on one screen: pageviews, visitors, bounce rate, referrers, top pages, countries, devices. The script is under 1KB, so visitors never see a consent banner. AGPL v3, Elixir, and the self-hosted Community Edition costs nothing to run. Community Edition is no longer the same product as Plausible Cloud. Funnels, user journeys, ecommerce revenue goals, SSO, the Sites API, and data center bot filtering are all Cloud only, and CE ships as a long-term release twice a year instead of continuous updates. Running it means Docker plus Postgres plus ClickHouse, and ClickHouse wants real memory. Cloud starts at $9/mo for Starter (one site, 10k monthly pageviews), $14/mo for Growth (3 sites, 3 seats), and $19/mo for Business (10 sites, funnels, revenue attribution), climbing with traffic inside each plan. Solo and small teams should just pay. Medium and large should self-host only if the CE feature set is actually enough. The catch: self-hosting buys you the dashboard, not the feature set. If funnels or SSO are why you wanted Plausible, you are paying either way. umami-software/umami is lighter with nothing held back, and PostHog/posthog answers the user-level questions Plausible will never touch.
Open source Calendly alternative
The Lens
Cal.com is open-source scheduling, the Calendly alternative you can run yourself. Share a link, people pick a slot, it lands on your calendar. The public code recently moved to a repo called cal.diy and relicensed to MIT, and for a solo user it's still free and self-hostable: unlimited bookings, your own branding, your data on your server. Here's what changed, and it matters. The open build was trimmed back to personal, non-production use. The features teams actually need, shared team scheduling, organizations, SSO, insights, now live in the proprietary hosted product, not the open repo. So the old pitch, "self-host the entire thing," no longer holds once more than one person is involved. On their cloud, a single user is free, Teams runs $12 per user a month, and Organizations is $28 per user a month. Solo users self-hosting cal.diy pay nothing and lose little. Teams have a real decision now: self-host the trimmed open build and rebuild the team pieces yourself, or pay for the hosted product like you would for Calendly. The "own everything" story is mostly a solo story today. The catch is the relicensing itself. Cal.com spent years as the AGPL open-core Calendly alternative, and a lot of teams adopted it on that promise. The core is still open and the solo experience is good, but the team features moving behind a proprietary wall is exactly the kind of shift you want to know about before you build a workflow on top of it.
Get the next issue in your inbox
Free. No spam. Unsubscribe anytime.