BANDURA Early access

Bandura Desktop — End User Licence Agreement

Version 1.0 · effective 2026-08-05

Licensor: Dmytro Lapchak, Lviv, Ukraine (“we”, “us”). Contact: [email protected]

This agreement covers the Bandura desktop application. It does not cover the open-source packages the app is built on — those are MIT-licensed and governed by their own terms (see § 8).

By installing or using Bandura you accept this agreement. It is written to be read; if any part of it is unclear, write to us and we will answer plainly.

1. The short version

Bandura is free to download and use. Nothing is locked, time-limited, or disabled without a licence — not on day 1, not on day 31, not ever.

If you use Bandura for paid work, you get 30 days to evaluate it, and then we ask you to buy one licence per person using it. That is the entire commercial arrangement. A licence is $59, paid once — it is not a subscription and nothing renews itself.

One payment. Twelve months of updates. The version you have keeps working forever. Your $59 covers every release we build in the twelve months after you buy. After that, the Bandura you already have carries on exactly as it is, indefinitely. A renewal buys only the releases built after that, and it is optional.

The rest of this document is the precise form of those sentences.

2. What you may do without paying

You may download, install, use, and keep using Bandura at no cost, with no time limit and no reduced functionality, for:

No account, registration, or payment method is required for any of the above. You may install it on as many of your own machines as you like, indefinitely. There is no trial, and nothing expires.

3. What requires a licence — and the 30 days before it does

A licence is required for commercial use: using Bandura in the course of work for which you, or the organisation you work for, are paid. This includes use by a company, government body, or other organisation, and use by a freelancer or contractor on client work.

You get 30 days from first installing Bandura to evaluate it commercially without a licence. No form to fill in and no permission to ask for — it starts by itself and we are not told about it. Evaluate properly: run it against your real APIs, put it in your CI, decide whether it earns a place. If after 30 days it is part of how you work, buy a seat.

When the 30 days pass without a licence, one thing changes: the app begins showing a dismissible note, at most once a day. Nothing is disabled, degraded, or made read-only, then or later. If you ever find a version of Bandura that takes something away when the 30 days end, it is not one of ours.

One licence per person who uses the software, not per machine — a single licensed person may install Bandura on their laptop, desktop, and a CI workstation. A licence is held by the person or organisation named on it and is not transferable between organisations.

Nothing in the software enforces this. It is a term of this agreement, and we rely on you to honour it. If you are a licensed user, the periodic reminder in the app stops appearing — the one exception is described in § 4, where a licence holder installs a release built after their update window — and that is a convenience, not the reason the term exists.

If you are unsure whether your use is commercial, it probably is — but write to us and we will tell you honestly, including when the answer is “you don’t need to buy anything.”

4. What a licence gives you — and what it doesn’t

A licence is a one-time purchase of $59 per seat. It is not a subscription: nothing renews automatically, we keep no card on file, and you will never be charged again unless you choose to be. What the $59 buys is two things — the software, permanently, and updates for a year.

The software, permanently. Every release you receive under your licence is yours to keep and to run for as long as you like. It does not expire, stop working, lose features, turn read-only, or degrade in any way when your update window ends — not then, and not later. Your licence is perpetual for the builds it covers.

Twelve months of updates. Your licence covers every release built within twelve months of the date you bought it, at no further cost — every bug fix and every new feature we ship in that period. The exact date is written into your licence key and shown in Settings → Licence, so it is never a matter of memory or trust.

Besides permission for commercial use, a licence also gets you:

When the twelve months end, nothing happens to the Bandura you have. It keeps working, unchanged, forever.

Releases we build after that date are not included in your purchase. Bringing them inside it means renewing. Renewal is entirely optional — you may stay on the version you have indefinitely, and many people will — and it costs less than the first purchase. We will publish the renewal price before anyone’s first window closes; until then we will not quote a number we have not committed to.

If you do install a release built after your window without renewing, one thing changes: the same dismissible note reappears, at most once a day, on that newer build. Nothing is disabled, no feature is removed, no file becomes read-only, and no downgrade is forced. That reminder is the entire consequence.

The update window is the only boundary. If a release is built inside your twelve months it is yours, and that includes a new major version. If version 2.0 arrives while your window is open, you get it; if it arrives after your window has closed, it needs a renewal like any other newer build. There is no second rule and no separate upgrade fee to work out.

Your key also records the version line it was issued for, shown in Settings → Licence. That is a record of what was sold, not a limit we apply — we would rather one clearly stated boundary than two overlapping ones. We will not release a major version purely to charge for it, and we will not remove features from an existing release to push you toward a newer one.

We deliberately do not promise updates forever. That is a promise nobody has managed to keep, and the tools that made it have quietly withdrawn it — which is worse for the people who believed it than never having offered it. What we sell instead is bounded and stated plainly: perpetual use of what you receive, twelve months of what comes next.

If we stop developing Bandura, your licence keeps working. Verification is offline and requires nothing from us. There is no server that can be switched off to disable the software you paid for, and no update window ending can take it away either.

5. Your licence key

Your key is issued to you by email after purchase and is verified on your own machine using a public key built into the app. It is never sent to us or to anyone else, and the app does not contact any server to check it.

The key states, in readable form, who it was issued to, the order it belongs to, the number of seats, the date it was issued, the date its update window ends, and the version line it covers. Settings → Licence shows the same details. We put the update-window date on the key itself so the boundary you bought is something you hold, not something we assert later.

Your key never stops verifying. When the update window ends, the key is still valid and the app is still licensed — the date only tells a build whether it falls inside what you paid for.

You may re-enter your key on any machine you use, and you may keep a copy of it. Please do not publish it, share it outside your organisation, or distribute it as part of any tool or image. A key that is published may be excluded from future releases.

We can re-send a lost key — write to us from the address it was issued to.

6. What you may not do

You may not:

7. Your data

Bandura stores your flows as plain files in folders you choose. We have no copy of them and no means of obtaining one. The application performs no telemetry, analytics, or error reporting unless you explicitly turn it on, and it makes no network request you did not ask for — with the sole exception of AI features, which contact the AI provider whose API key you supply, under that provider’s terms.

Your work is yours. Nothing in this agreement grants us any right to it. If you stop using Bandura, your flows remain readable, runnable text files.

8. Open-source components

Bandura is built on open-source software, including Electron, Chromium, Node.js, React, and Monaco, each under its own licence. The Bandura packages that make up the execution engine, file format, CLI, and MCP server (@bandura/*) are published under the MIT licence and are not restricted by this agreement. Their licences are reproduced in the application’s about screen and in the source repository.

9. Refunds

If Bandura does not do what you expected, write to us within 30 days of purchase and we will refund you in full, without argument and without requiring a reason. Because the software is free to use before you buy, we would rather you evaluated it first — but the refund stands regardless.

Refunds are processed by our payment provider, who is the merchant of record for your purchase and whose terms also apply to the transaction.

10. No warranty

Bandura is provided “as is”. To the maximum extent permitted by law, we make no warranties, express or implied, including of merchantability, fitness for a particular purpose, or non-infringement. We do not warrant that the software is free of defects or that it will run uninterrupted.

This does not exclude or limit any statutory rights you have as a consumer that cannot be excluded under the law of your country of residence.

11. Limitation of liability

To the maximum extent permitted by law, our total liability to you under or in connection with this agreement is limited to the amount you paid for your licence in the twelve months before the claim arose (or, if you paid nothing, to nothing).

We are not liable for indirect or consequential loss, loss of profit, loss of data, or business interruption. Bandura executes requests against systems you point it at; you are responsible for which systems those are and for the consequences of running a flow against them.

Nothing here limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be limited.

12. Termination

This agreement ends if you stop using Bandura and delete it, or if you materially breach it — in particular § 6. If we terminate for breach, sections 7, 10, and 11 survive.

We will not remotely disable or revoke a licence that was paid for. The end of an update window is not a termination: it ends nothing, revokes nothing, and leaves the software you hold untouched.

13. Changes to this agreement

We may publish a new version of this agreement for future releases. The version in force for you is the one published when you bought your licence, and it continues to apply to every release covered by that licence — including after your update window ends, for as long as you keep using those releases. We cannot change the terms of a purchase you have already made.

If you later renew, the agreement published at the time of that renewal governs the releases the renewal covers. It does not reach back and change the terms of the builds you already have.

Every version is kept in the source repository’s history, so you can always see exactly what changed and when.

14. Governing law

This agreement is governed by the law of Ukraine, without regard to its conflict-of-law rules. If you are a consumer, you keep the protection of the mandatory law of your country of residence, and you may bring proceedings in its courts.

Questions about any of this — including “do I actually need to buy a licence?” — go to [email protected] and get a straight answer.