New Developer Tools Worth Knowing — November 2026
This is the third monthly round-up of tools that came in through our submission form and survived a look. The October edition has the previous five, and the September edition has the first.
“Survived a look” still means the same thing. I checked the claims I could check, on 7 November 2026, against each vendor’s own pricing page, docs or repo. I haven’t put any of these through real work yet. Where something couldn’t be confirmed, I say so rather than guess. All five arrived through the free form, nobody paid anything, and I didn’t contact any of the vendors while checking.
This month’s batch is a bit more mixed than the last two. One hosted monitoring service, two very small open-source projects, a database host and a cloud browser for agents.
PingCron — heartbeat monitoring for cron jobs
The homepage tagline says it plainly: “Know when your cron jobs miss a check-in.” You have your scheduled job ping PingCron when it finishes, and if the ping doesn’t turn up within a grace period, you get an alert. It’s the kind of tool you don’t think about until a nightly job has been failing silently for longer than you’d like to admit. Logs only help if something reads them.
Checked 7 November 2026: Free is $0 a month for 5 monitors, 7 days of history and 1 account owner, and the homepage says no credit card is required. Pro is $9.99 a month for 50 monitors, 30 days of history, custom webhooks and still 1 owner. Team is $29 a month for 200 monitors, 90 days of history, 10 team members and public status pages. Business is $79 a month for unlimited monitors, a year of history, an unlimited team and priority support. Source: pricing on the homepage.
Worth knowing: there’s no separate pricing page. The obvious URL, pingcron.io/pricing, returned a 404 when I checked, and the full table sits on the homepage instead, so link people there. The homepage also says you can connect “Claude, ChatGPT, or Codex” to PingCron, and that those connections are “included on every PingCron plan, including Free”. I haven’t tested that against a live connection, so treat it as their claim for now. The jump that matters is from Pro to Team, since Pro keeps you at a single owner and Team is where other people get in.
gh-pull — a pull request dashboard for the GitHub CLI
From the repo description: “GitHub CLI extension for a local pull request dashboard. Group PRs by repository, monitor reviews and CI checks, and merge from your browser.” The README puts the pitch as organising PRs across repositories “using your existing GitHub login”, which is the part I like. No new account and no new token to manage. It rides on whatever gh is already signed in as.
Install is gh auth login --hostname github.com, then gh extension install shiqicao/gh-pull, then gh pull. If you’d rather run it from source, clone the repo, sign in the same way, run npm start and open http://localhost:3000.
Checked 7 November 2026: 4 stars, 1 fork, MIT licence, written in JavaScript, 1 open issue. The repo was created on 9 October 2026 and was last pushed to on 7 November, the day I checked. Extension mode needs the GitHub CLI, and source mode needs Node.js 22 or newer. It works with GitHub.com accounts only. In the README’s words: “A GitHub.com account is required; GitHub Enterprise hosts are not supported.” Sources: repo, GitHub API, releases.
Worth knowing: it’s a month old with single-digit stars, so there’s very little outside experience to lean on. It’s also moving fast. There were nine tagged releases between 28 October and 7 November, v1.10.0 through v1.13.1, which is great if you want fixes and less great if you want things to sit still. If your company runs GitHub Enterprise, stop here.
Postquel — a native macOS PostgreSQL client
The repo describes it as a “Native macOS PostgreSQL client with bring-your-own AI (work in progress)”, and I’d take the “work in progress” at face value. As someone who lives in Xcode, I’m always glad to see a Mac database client written in Swift rather than another browser tab in a wrapper.
The “bring-your-own AI” part works differently from most. There’s no API key field. The v0.1.1 release notes put it in one line: “For the assistant, install and sign in to Claude Code, Codex or Cursor Agent”. So it borrows an agent you already have set up.
Checked 7 November 2026: 3 stars, 0 forks, MIT licence, written in Swift, 0 open issues. The repo was created on 17 September 2026 and last pushed to on 5 October. It’s free and open source, and there’s no pricing page because there’s nothing to buy. It needs macOS 15 or later and runs on both Apple silicon and Intel. You don’t need a separate PostgreSQL install, because libpq comes bundled. The v0.1.1 DMG is signed and notarized by Apple, and the release page publishes a SHA-256 checksum you can check the download against. Sources: repo, v0.1.1 release, product page.
Worth knowing: the submission pointed us at frizky.dev/products/postquel, which is a personal site, but the code and releases live at github.com/frizurd/postquel. It’s the same product with a different front door, not a rename. Go to the repo if you want the actual build. Like gh-pull, it’s very young, and nothing had been pushed for about a month when I checked.
Layerbase — hosted databases across a lot of engines
The page title is “Serverless and Managed Databases for 19 Engines”, and the homepage goes on: “Run Postgres, MySQL, Redis, SQLite, FerretDB, and more. Branch for isolated previews. Always-on production from $5/month. No usage meters.” That last line is the bit I’d pay attention to. Flat pricing is easier to budget than metered compute, and metered compute is how most people get surprised by a free-tier database bill. If you’re comparing options, our free-tier databases round-up covers the more established ones.
Checked 7 November 2026: Free is $0 a month for 2 databases, 5 GB of storage and 20 concurrent connections, across 9 Standard engines: PostgreSQL, MariaDB, Redis, Valkey, DocumentDB, SQLite, DuckDB, TypeDB and libSQL. Solo is $5 a month for 2 databases, 10 GB and “11 Standard engines (+ MySQL and FerretDB)”. Pro is $15 a month for 10 databases, 25 GB and “All engines: Standard + Performance”. Dedicated is “From $35/mo per server”, and the card says there’s “No database or branch cap on the server”. On Pro you can add pool blocks at $10 per block per month, and the page says “Each block adds 1 GB of always-on RAM, 1 vCPU, and 25 GB of storage to Pro.” The self-serve dedicated servers come in three sizes, US prices: Dedicated 4GB at $35 a month (2 vCPU / 4 GB / 25 GB), Dedicated 8GB at $65 (4 vCPU / 8 GB / 50 GB) and Dedicated 16GB at $120 (2 vCPU memory-optimized / 16 GB / 100 GB). Sources: pricing page, homepage.
Connections on Solo are where the page argues with itself. The Solo card says “Uncapped, pooled connections”. The FAQ further down the same page says Free “is capped at 20 concurrent connections (Solo raises that to 100, Pro to 500)”. Those can’t both be the whole story, and I’m not going to guess which one is current. If connection count matters to you, ask them before you pay.
Pro comes with a trial, and the FAQ’s wording is “Start Pro and pay nothing for 7 days - every engine, the always-on pool, 30-day backups, all of it.” Read the next sentence too: “A card is required at checkout but you’re charged $0 up front; on day 7 the subscription converts to $15/mo automatically.” Put a reminder in your calendar.
Worth knowing: MySQL isn’t on the free plan. It starts at Solo, along with FerretDB, so if MySQL is the reason you’re looking, budget $5 from day one. Agent servers, which Layerbase calls workspaces, are billed separately from the database plans, starting at $10 a month per workspace in three sizes. And all of this is beta pricing: the pricing page says “during the beta period (June 2026 to July 2027), plans and limits may change”, that paid-plan changes are announced at least 60 days ahead, and that “Free plan features may change without notice.”
Cloudbrowser — a persistent Chrome for agents
In its own words: “A persistent Chrome cloud browser for AI agents.” Each browser is an isolated environment that keeps its login state, and an agent can reach it remotely, pause it, resume it and fork it. Saved logins are the useful part. Anyone who’s had an agent run into a fresh login wall on every single run will see why.
It connects over the Chrome DevTools Protocol, and the homepage lists Playwright, Puppeteer, Cursor and Claude Code among the things that can drive it.
Checked 7 November 2026: Free is $0 a month for 1 browser-hour and 1 browser running at a time. When the hour runs out, running browsers pause automatically, so there’s no overage. Anyone with a verified email can sign up. Basic is $20 a month for 250 browser-hours and 10 concurrent browsers, then $0.08 per browser-hour after that. Pro is $99 a month for 1,250 browser-hours and 100 concurrent browsers, then $0.06 per browser-hour. The free plan reads the same on the homepage and on the pricing page. Sources: pricing page, homepage.
Worth knowing: browser-hours add up across every browser you have running, not by the clock on the wall. The pricing page’s own example is “10 browsers × 30 minutes = 5 browser-hours.” On the free plan you only get one browser at a time, but one forgotten session left open over lunch is most of your month. The pricing page also says Pro customers can ask for higher concurrency “at no extra fee”. I can’t check that without an account, so I’m passing it on as their claim and nothing more.
How tools get into this round-up: they arrive through our submission form, they have to be for people who build software, and I verify what I can before writing. Free editorial coverage is at our discretion with no timeline. The standards page sets out how we review and what money does and doesn’t buy. Nothing in this piece was paid for.
Verified 7 November 2026 against each project’s own repo, docs and pricing pages.
Comments