Building trust before asking for a credit card

The trust problem in desktop software

Before you pay for desktop software, you should be able to test it on your own footage, see every price, and read the terms in plain language. KwaFlux is built for that: the installer needs no account, previews run free on your clips, and the price list and legal pages are public. This post explains each check.

• No account wall before download
• Free 1s/3s/5s previews on your own clips. A paid plan is needed to export, convert, repair a file, or download a file from a link
• Plain-language refund and subscription terms before checkout

Download first, account later

• Direct installer link — no email gate or waitlist form
• Explore the full UI before signup
• No sign-in needed to explore the app; the account is where billing and devices live

Pricing that respects your time

• Every plan and billing cycle listed on one page
• No hidden fees, no "contact sales" tier, no fake countdown urgency
• Per-month equivalents shown so billing cycles compare instantly

Legal pages that are actually readable

• Privacy — what is collected, and what local processing keeps on your machine
• Refund — window and process in plain language
• Subscription terms — cancel, what the Perpetual License covers, device policy

Honest product communication

• No "every clip becomes RED-camera" claims
• Feature pages state what each module does not do
• If a requirement is narrow (e.g. macOS 12+ Apple Silicon only), we say so — see download

What you can verify before you pay

A buyer can settle three questions before a card is involved: what the local preview does on a clip they already know, what the license actually says, and which outcomes the product does not claim. None of those questions needs a sales call. The installer, the pricing page, and the legal pages are public, and the short preview runs with no account.

Start with a file you would hate to get wrong. Download KwaFlux, open a workspace, and import that clip. Render one second, three seconds, and five seconds of the module you are considering. Those previews run locally, in the same workspace you would export from. They are long enough to judge and short enough to throw away. Watch the frames you would pause on in a client review: a face, a textured wall, a moving edge. If the preview adds a smear, a plastic-looking patch, or an edge you would reject, stop there; you still haven't bought anything. If the change is one you could defend on that clip, you now know something real about this file, though not yet about the rest of the timeline.

Read the preview as a narrow test. It can show whether this module, on this file, is worth running; it cannot stand in for a different shot, a harder pan, or a lower bitrate. Keep the source frames next to the preview and compare those seconds only. You see a local result before anything is bought.

The second check is the license, and so far you have only installed the app. Pricing lists every plan side by side. The subscription terms and the refund page cover cancelling, devices, and refunds in ordinary language. If the pricing page and a legal page ever seem to disagree, follow the legal page and ask before you pay.

The third check is the list of outcomes we do not claim. Privacy explains what is collected and what is processed on your machine. Feature pages state what each module does not do, and the download page names the platforms in scope. If a limit you care about is not on those pages, treat it as unanswered and ask.

Do the three checks in that order, and pay only if each one still matches the job: preview your own clip, read the pricing and legal pages, and read the feature page for the module you previewed, including what it does not do.