for people who write plugins
SmartManiaa handles payment, copy protection and the storefront. You focus on what you do best.
x-api-key: •••••••••••• // request { "license_key": "EASYTOOLS-7B2K-9X4M-PQR3", "machine_id": "a3f2c8…", "product_sku": "sket_easytools_clean", "product_version": "1.0.0" } // 200 OK { "message": "Licença válida.", "status": "valid", "update_available": false }
licence active · machine linked
real API request and response — example values, structure faithful to what runs
Licenses. Issues the key, validates on every launch and binds it to one computer. Switching machines is a request with email confirmation and a waiting window — a real restriction, and it's what keeps the price per person.
Charges, and the money is yours. The customer pays into your Stripe account, not ours. The platform keeps a percentage commission on the transaction itself — you're not waiting for anyone's payout.
Delivers, and keeps delivering. The file and every update arrive through the Hub. You publish a new version and it shows up for the people who already have it — no mailing list, no .rbz over WhatsApp.
None of this is a roadmap. It's the infrastructure that distributes EasyTools today, in production — the whole catalogue runs on it.
Hub for SketchUp is an extension that opens the platform in a window of SketchUp itself. People who design find, install, activate and update without switching apps and without leaving the model.
It's where EasyTools shows up today — and where another developer's product would show up. Not in a tab someone has to remember to open, but in the toolbar they're already working in.
And the product goes out with your name on it: every card in the catalogue says who wrote the plugin, and the storefront keeps publishers separate — today there are two, and the rule is the same for whoever joins: whoever writes it is who publishes it.
Then the whole list shows up, and every item is a system: a trial period. A licence that expires. A paid upgrade from version 1 to version 2. Selling outside the store too. Getting paid. And working out who the seller of record is for tax — because someone is issuing that invoice, and it might be you.
None of them is the plugin. And all of them have to exist before the first sale.
License protection is a whole system, and it's the most expensive thing to build alone. Here it belongs to the platform, in two layers: the plugin layer — key, machine, validation — which runs today; and the Hub layer — the machine tied to the account, and the lock — which is specified. Every piece below states its own status.
a licence's path · the layer that runs
The customer buys, or downloads the free one. The payment processes into your Stripe account and the licence is born on its own — you don't issue anything by hand.
The first launch binds the machine. The system registers the computer, and the key becomes valid there — on one, not on a hundred.
On another computer, it doesn't validate. No online proof of validity, no plugin — and renewing that proof needs an internet connection.
A machine switch doesn't become your support ticket. The customer sorts it out: from the machine itself, right away; remotely, by email with confirmation and a waiting window between switches.
| Mechanism | What it does | Status |
|---|---|---|
| Machine binding | A key is good for one computer. Switching is requested from the machine itself — possession is the proof — or by email with confirmation and a waiting window between switches. | Runs today |
| Validation on every launch | No proof of validity, no plugin. Needs internet to validate the licence, and the validation repeats. There's no version that runs offline without ever revalidating. | Runs today |
| Server-side switch | Free becomes paid, and a licence becomes revoked, on the server's next answer — without breaking anyone's install and without a new release. It's the same switch that closes a beta. | Runs today |
| Account lock | A plugin only validates if the Hub on that machine belongs to the same account as the key. It kills the borrowed key — your friend's Hub is signed into your friend's account — and for the person who paid it's the opposite of a lock: the licence follows the account, not the computer. | Specified |
| Per-install record | Every install recorded, with a last-seen per machine. Who uses it, who stopped, and who switches computers suspiciously often — visible before it costs you money. | Specified |
2 rows in that table haven't been built yet, which is why they're marked. Specified means written spec with a decision made — not vague intent. And when they land, they land server-side: they apply to everyone with no plugin release, including people who already installed.
The program's commercial model is being defined, and a number that doesn't exist doesn't go on this page. What can be stated: the price goes public before the program opens — and before anyone is charged. People on the waiting list will know when that happens.
Coming soonprogram price · being defined
None of these paths is bad — they're the ones that exist, and each leaves part of the work with you. The comparison is about where the work lives, not about who the villain is.
| SmartManiaa | Extension Warehouse | SketchUcation | Direct salesGumroad · your own site | Your own server | |
|---|---|---|---|---|---|
| Licensing built in | ✓ | ✓the checks go into your code | ✓the store's own system | — | ✗you write the system |
| Machine binding | ✓one computer per key | ✓up to two instances | — | — | ✗if you build it |
| A storefront ready, with your name | ✓ | ✓ | ✓ | ✗you build the page | ✗you build everything |
| Updates arrive on their own | ✓through the Hub | — | — | ✗the channel is you | ✗you build the updater |
| Billing handled by the channel | ✓into your Stripe account | ✓ | ✓ | ✓by the processor | ✗you wire the gateway |
| What's left for you | writing the plugin | implementing the checks and the vendor process | integrating their licensing system | all of the protection | everything: machine id, server, checks |
✓ built into the channel · ✗ left to you · — no claim: we found no source to back the cell.
Does the sales money pass through SmartManiaa?
No. The customer pays into your Stripe account, and the platform's commission is kept on the transaction itself — you're not waiting for anyone's payout.
Do I need my own Stripe account?
Yes. The account is yours and the money lands in it. The platform connects to your account to process the sale and issue the licence.
Whose job is support?
Platform questions — payment, licence, access — are SmartManiaa's. Product questions are answered by whoever wrote it: whoever writes the code answers the support.
Does it work for software other than SketchUp?
Not today. The platform distributes SketchUp plugins, and no other program is running.
How much does publishing cost?
Not public yet. The model is being defined and the price comes out before the program opens — until then, no surface of the site shows developer pricing.
The waiting list records your interest — joining requires an account, costs nothing and commits you to nothing. When the program opens, the notice shows up in your account, with the terms already public. And it notifies, it doesn't rank: nobody gains a position by arriving first.