Is a monthly plan really a subscription?
No — a monthly plan is not a subscription, and this
is the question we most want to be unambiguous about.
The monthly plans are payment schedules for the same permanent
license. When the final payment clears, the license is yours and there
is nothing further to pay, ever. There is no code in FoundrySuite that
checks whether you have paid this month, because a local application
cannot phone home and we did not build it to try.
What do I get after paying on a plan?
The installer, on a page only you can reach, and a license file
emailed to the address you paid with — one per workstation you
register. Paying is not
quite the last step: every license is bound to the machine it
may run on, and the fulfillment page the receipt links to
walks you through that in two minutes — run
leadflow license fingerprint on the
machine, paste the output, and the signed file is emailed to
you and downloads from the same page. What you install is the
same program you evaluated, with nothing switched
on or off — the only difference is that the
paid build reads that license instead of ignoring it. The
check is entirely local: it reads one file, verifies a
signature against a key built into the program, and never
contacts anyone. That is also why it keeps working with the
network unplugged. If you want to know what you are
installing before you decide, the
install page covers it.
Why do the monthly plans cost more in total?
Because a payment schedule carries risk that a single charge does
not. The 12-month plan is nine percent over the outright price and
the 24-month plan is twenty percent, and both numbers are written on this page
next to the monthly figure rather than left for you to add up.
What if we move to a bigger machine?
The fulfillment page your receipt links to issues a license
for each machine you register, so moving is two minutes and
no conversation — the fingerprint command tells the page
which machine is asking, and the file follows the same
afternoon. A license is tied to one workstation so a single
purchase cannot be copied around a company, but nothing about
it is a dongle: it is a file, not a piece of hardware. If the
page cannot do it — a machine with no stable identifier,
or a move you would rather not explain to a form — one
email to us reissues it free, for as long as you own it.
What if we need more workstations?
Buy another license for the extra machine —
the application does not count seats, so the conversation is
a commercial one rather than a technical block. And a business
that has outgrown one machine is one we would rather talk to than
meter.
Can we share one license across a few people?
Ask us. The application does not count seats, so the conversation is
a commercial one rather than a technical block — and we would
rather do that honestly than have you discover a limit later.
What about support and updates?
The support page says what we answer, by
whom, and what we have not decided. We would rather say that than sell you
a support tier you may never use.
What if it turns out we do not want it?
That is what the thirty-day trial is for. It
needs no card and no payment step, which is why we encourage putting your
own data into it before you pay for anything. A refund for a purchase you
regret is not something we have decided; the
support page says so rather than inventing a policy.