Someone typing queue management system open source or booked open source into a search box is asking for two things at once. The first is the price: no subscription, no invoice arriving every month whether the software gets used or not. The second is control: the right to open the code, change it, and not need anyone's permission to keep running it. An open-source license answers both of those wishes at the same time. A license bought from a store answers only one of them, and which one depends on exactly what the seller wrote into the license, not on what self-hosted or one-time purchase imply by themselves.
An Ownware license is not an open-source license. It is a one-time purchase of source-available software, and those two things sound close enough on a product page that the difference is worth stating before anything else, in the license's own words rather than a summary of them. Here is the whole clause, verbatim from the license page (read 2026-09-07), on what neither tier -- single or extended -- lets a buyer do:
"redistribute, resell or sublicense the software or its source to anyone else, offer it (or something derived from it) to other people as a hosted or multi-tenant service they sign up for -- that needs a separate SaaS agreement -- or strip out the copyright and license notices."
Read that plainly, because it is not written to be softened. No passing the source on to someone else. No selling it on. No putting it behind a signup page for other customers to use as their own service, even a free one. No deleting the notice that says who wrote it. None of that is unusual for a bought license, and none of it is what an open-source license would say -- an open-source license exists specifically to permit most or all of exactly this. The gap between the two is not a technicality on a legal page. It is the entire content of the word open.
What the license grants instead
Buying does grant something real, and it earns the same precision. Two tiers exist, and the store's own wording for each, read the same day, is this.
The single license lets a buyer "install and use it on one (1) domain or subdomain you own or operate, modify the source freely for that installation, and use it commercially to run your own business -- including doing client work on it." One domain, full source access for that one installation, and commercial use is stated outright: an agency billing a client for work built on it is inside the license, not skirting it.
The extended license adds "everything the single license grants, on as many domains as you own or operate, plus up to ten (10) client installations, one per client project." That second half is the one people miss. The extended license does not just widen how many of a buyer's own sites can run the software; it separately covers up to ten installations built for clients, each one handed over to that client or hosted for them, which is the shape of work an agency or freelancer actually has more often than the single-domain case.
The two searches this page answers point at two products directly. Tokora is a self-hosted queue and token display: it issues numbers, calls them to counters, and runs the waiting-room board -- the category behind queue management system open source -- and it is Tokora, $69.00 single license, $149.00 extended. The other search is for booking software; the store's own rent calculator compares Slotly against Square Appointments at $49.00 a month (read 2026-09-07), and Slotly itself is $99.00. Both are modify-the-source-freely, one-time purchases under the terms just quoted, not open-source releases, and neither pretends otherwise on its own page.
Try the Tokora demo ↗Live, on sample data, no sign-up.
The honest answer to what if the vendor disappears
The strongest real argument for open source is not the price. It is continuity: a project with public source and a permissive license keeps working, and stays maintainable by someone, even if the people who wrote it walk away. A license bought from a single seller does not obviously offer that, and leaving the question unanswered would be dishonest. So here is the store's own clause on it, adopted 23 August 2026 and written into the LICENSE.txt that ships inside every product, which means it binds the operator itself and whoever the operator's rights ever pass to, not only the buyer:
"If we do not publish a stable release of a product for 365 consecutive days, that product is considered no longer actively maintained, and for everyone already holding a license the single-domain limit is lifted: run your copy on as many servers as you own or operate, and commission any developer you choose to maintain it. If no stable release is published for three consecutive years, the software in its last published form becomes available to existing license holders under the MIT license, automatically."
Two thresholds, two effects. A year of silence lifts the domain limit for anyone already holding a license -- it stops being tied to one installation and becomes tied to the buyer instead, free to run wherever they operate and to be maintained by whoever they hire. Three years of silence releases the last published code under the MIT license automatically, to existing license holders, with nothing to ask for, sue over, or negotiate. That does not make the license open source today, and it should not be read as if it does. It does mean the abandonment scenario -- the one open source is usually bought as insurance against -- has a written, dated answer here as well, and the clause is built to bind successors specifically so a change of operator cannot quietly undo it.
Who should choose open source instead
This is the part a sales page normally leaves out, so it gets a real section rather than a line at the bottom.
If the plan is to redistribute the software to other people, resell it, fork it in public, or build it into a signed-up hosted service that other customers pay to use, an open-source project is the right tool and this store's license is not it. Nothing above changes that. The clause quoted at the top rules out every one of those uses in plain words, for both tiers, and no reading of the continuity clause gets around it while the software is still being actively maintained. Anyone with that plan should be looking at an open-source project in the category, not a one-time license here, and there is no version of this license that becomes the right answer for it later.
It is worth being just as honest about what open source does not hand over, because open source gets treated as a synonym for supported, and it is not one. Nobody is contractually on the hook for an open-source project either; most run on whatever time their maintainers choose to give, which can be a great deal or can be none at all, and picking one is its own kind of bet. The software sold here sits in a similar spot on that specific point. It is "provided as-is, without warranty -- normal for source-code products, and the reason every product has a free live demo you can try before buying," and support is "best-effort by email for installation and defects in the delivered code -- it does not include custom development, server administration, or modifications you make to the source." A license bought here trades the right to redistribute for a fixed price, a working demo to try first, and the continuity clause above. It does not trade it for a support contract, because that is not what either kind of license, open or bought, actually promises.
If the plan is one installation -- a queue board or a booking calendar, on one domain, run by the buyer or a single client -- the single license covers modifying the source freely and using it commercially, at a fixed and known price: Tokora at $69.00, Slotly at $99.00. If it is more than one domain, or a build handed to a client, the extended tier is the one written for that. If it is redistribution, resale, forking, or running the software as a service for other signed-up customers, none of that is licensed here on either tier, and an open-source project is the honest place to look instead. The full terms, including everything quoted above, are on the license page.