Over the past four years, AL Object ID Ninja has quietly kept thousands of teams out of conflict trouble. To plan the next chapter responsibly, I need a simple signal from you.
What I’m asking
If you intend to keep using the hosted Ninja backend after 1 January 2026, please register your interest here:
👉 alid.ninja
This is not a subscription. It’s a no-commitment way to:
- Lock a 35% lifetime “super-early-bird” discount
- Help me finalize fair pricing and plan my activities in the transition period
- Potentially lower the final prices for everyone (more committed teams → better economies of scale)
Your two paths (both remain available)
- Stay on the hosted backend (premium): zero setup, zero maintenance, zero hassle (just like in the past) + new features + support + the upcoming management portal + mobile app.
- Run your own backend: Ninja remains open to self-host on your Azure subscription, at your pace, under your control, but with you carrying the infrastructure cost, maintenance costs, and costs of supporting users who get stuck.
Why this matters now
To operate a reliable, supported, and evolving hosted service, I need to know roughly how many teams plan to stay. If there’s sufficient interest, I’ll proceed and continue investing in the hosted platform. If there isn’t, the shared backend will be shut down on 31 December 2025, and all teams will continue with their own deployments.
This is not pressure—just transparency. Running Ninja at scale carries real cost, and I want to make the right decision with you, not for you.
A straightforward pledge
My goal is simple: keep Ninja effortless for those who prefer a smooth experience on a managed service, and keep it open for those who prefer to run it themselves. If you’ve found value in Ninja and want the hosted option to continue, please raise your hand now:
Thank you for helping me plan wisely—and for everything you’ve built with Ninja so far.
Thank you for providing this free for as long as you have Vjeko. Open source is one thing but a service to run it is another.
Thanks, James!
Hi Vjeko,
Also thanks for providing this to the community for so long now.
There is a question in the subscription page Number of Apps.
What exactly do you mean by this?
Is this the number of .objidconfig files we’re using in our different workspaces?
Or the number of repositories?
Hi Job! It’s the number of different app.json files that are under control of Ninja. Essentially, every different id from app.json counts here. Depending on how many companies decide to go with Ninja, I may even drop the per-app pricing completely and keep only the user prices.
Hi Vjeko.
Also, the question about “Number of Users” – what does it mean? Concurrent users? Total users? And what is a relation to “Number of Apps”?
For example, there is a workspace with 10 apps and there are 2 developers. And, there is another workspace with 5 apps and 3 developers (2 of them are a part of the first workspace). What should we enter into the request form?
Hi Vjeko.
Also, the question about “Number of Users” – what does it mean? Concurrent users? Total users? And what is a relation to “Number of Apps”?
For example, there is a workspace with 10 apps and there are 2 developers. And, there is another workspace with 5 apps and 3 developers (2 of them are a part of the first workspace). What should we enter into the registration form?
Hi Radovan,
Number of users is number of named users. If you have total of 20 apps and total of 3 developers, then it’s 3 users and 20 apps.
Hi Vjeko, in my organization we need to due a vendor vetting process. How can we get the formal billing information to get this started? There is likely a form for you to fill out but I will get the details from our procurement group.
What happens 01/01/26 if we are not signed up? I have expressed interest to you but our procurement process can be slow sometimes. Is there any grace period?
Hey Todd,
Ninja will be your typical SaaS product: you go online, subscribe, leave credit card number, get monthly invoices/receipts – all this handled through Stripe (I don’t handle your credit card or billing). All in all, this will be the same as with any other SaaS. I don’t know how this works in corporations such as yours, but I am pretty sure companies like yours don’t really vet Microsoft, Google, Amazon, OpenAI, Anthropic, or whoever else you are using for SaaS products.
On 1/1/26 what will happen is:
– Ninja will nag you to subscribe if you haven’t subscribed yet
– everyone gets a pro-bono one month to migrate
– anyone who subscribes during January will get January billed at the end of month
– anyone who uses Ninja during January without subscribing, and migrates to their own endpoints during January will not be billed – it’s on the house 😊
– anyone who used Ninja during January without subscribing and migrated to their own endpoints and later choses to subscribe to Ninja will get January billed together with the first invoice
– if you are still on public Ninja endpoints on 1 February 26 and you haven’t subscribed, then Ninja stops serving numbers
If you still want to stay on public endpoints and you still absolutely must vet me (actually, my company), then please wait a couple of weeks until I publish the website. Either way, you have a full month of January to transition smoothly, either direction.
I hope this is a satisfactory answer.
/Vjeko
Hi Vjeko,
I have tried to set up subscription “Pay as you go” and error appeared “Failed to create checkout session: Quantity should not be specified where usage_type is
metered. Remove quantity fromline_items[0]”. Can you help me with that?Hi Roman,
Yes, I’ve noticed that bug. Sorry for not seeing your comment earlier (or the bug either). It was a problem in my production environment Stripe setup. It all worked fine in development, but I messed up slightly in Production. I am working on the fix, it should be up and running shortly.
Thanks for subscribing!