This past weekend marked an important milestone for AL Object ID Ninja.

Backend version 3 is now live, running in production on:

• brand-new endpoints,
• the latest supported Node runtime,
• and fully covered by more than 1,300 automated tests.

So far, it’s been running smoothly and reliably, exactly as intended.

At the same time, version 3 of the VS Code extension was published to the Visual Studio Code Marketplace earlier today and has already started being used in real production environments.

This post is a short status update: what’s live, what changed, what to expect next, and how billing and pricing work going forward.

This post is for teams running AL Object ID Ninja on their own backend.

If you are using the hosted Ninja backend, you don’t need to do anything — the transition will be handled for you invisibly.

When I opened the early-bird sign-up page for AL Object ID Ninja, my goal was simple:
to understand whether there was enough real interest in a fully supported, commercial-grade Ninja platform for me to commit myself to building it the way it deserves to be built.

That question didn’t stay unanswered for long.

The response was overwhelming — a clear, resounding “Yes, please!” from the market.
To everyone who signed up: thank you. Truly. Your trust is the single biggest motivator behind the speed and intensity of development happening right now.

I even extended the early-bird window by two extra days to accommodate the late rush, but now the big lifetime discounts are officially closed and I’m no longer collecting “count-on-me” registrations.

That said, if you feel you should still receive a discount, reach out to me directly before December 22, and I’ll gladly provide a 15% voucher. No justification needed — just ask.

Every now and then a real story captures the essence of what a product is meant to do. This one did that for me.

A few days ago, LS Retail, a long-time Ninja user, reached out and asked a simple question:
“Can you help us move from our private endpoints to your hosted backend?”

At first, this surprised me. LS Retail has been using AL Object ID Ninja literally since day one—the very day it was released. Not only that: they never used the public backend. From the beginning, they chose to run Ninja entirely on their own infrastructure.

Fun fact from the past three months of AL Object ID Ninja:

Ninja has handed out object IDs to 9,365 apps.
Out of those, 297 apps were configured to use private endpoints.
But here’s the interesting part:

Only 122 apps were consistently configured correctly for all team members — meaning every team member configured private endpoints in their instance to make sure numbers were actually coming from their private endpoints as intended.

That means:
✅ 3.2% of teams chose private endpoints
⚠️ but only 1.3% set them up in a fully reliable way

For everyone else, running a “free” backend isn’t really free — it either means constant discipline to keep things in sync, or the occasional manual conflict cleanup. And that hidden maintenance probably costs more time (and money) than a premium subscription ever will.

If you’d rather choose hassle-free forever, now’s the moment to secure your 35% lifetime super-early-bird discount.

The early-bird window closes November 22.

👉 alid.ninja

Work smarter, not harder. Let Ninja do the boring parts.