Template Marketplace
Your customers deploy ready-made stacks — templates — into an environment in one click, from Stacks → Templates in their dashboard. The catalog is hosted on kuploy.app; this page covers what it means for you as the operator: who can deploy what, and how the paid tier is gated.
For how your customers use it, see Templates.
Access tiers
Every template is free, pro, or cloud:
- Free — any of your customers can deploy it.
- Pro / cloud (paid) — gated against a kuploy.app product (e.g.
kuploy-cloud), reusing the billing you already run. No separate paywall.
How paid templates are gated
A paid template requires the customer organization's own active paid plan — one of the plans you define in Manage Your Plans, not the default/free tier. A free-plan org that tries to deploy one gets an Upgrade prompt linking to your pricing. The check is per-organization, against the plan you assigned them.
Keep your license entitled
Paid templates reference a kuploy.app product (e.g. kuploy-cloud). For
kuploy.app to release a paid template's spec to your deployment, your
kuploy.app license must be entitled to that product. If it lapses, paid specs
stop being served — even to organizations you've already put on a paid plan.
Keep your subscription active (see Your Subscription).
Free templates are unaffected — their specs are served without any license.
Private images pull themselves
Some paid templates ship a private image — the software is not public, so the deployment needs a credential to pull it.
There is nothing for you to configure. kuploy.app sends the credential to your cloud on licence sync, and your customer's deployment uses it automatically. You never copy a token into an environment variable, and you never see it in a settings page — it is the platform's credential, not yours.
Two things follow from that, both worth knowing:
- It arrives on a sync, not instantly. A newly entitled tenant may wait one sync interval before a private image will pull.
- It goes away the same way. If your entitlement to the template lapses, the next sync removes the credential. Deployments already running keep running; new ones stop being able to pull.
A deployment whose image cannot be pulled looks healthy in the dashboard — the stack provisions, and the failure is in the pod that cannot start. If a customer reports a paid template that deploys but never comes up, check your entitlement to that template first.
List your cloud in the public gallery
The gallery on kuploy.app does not deploy anything itself. When a visitor picks a template, they choose which cloud to deploy it on — and yours can be one of the choices.
This is opt-in, per template, and off by default. It has to be: one global switch would publish your whole purchase history on a page anyone can read, and you may resell one template without saying what else you run.
To appear as a provider for a template, all four must hold:
| You asked for it | per template — listing one does not list the others |
| Your address is confirmed | kuploy.app checks that the address you published is really your deployment, and rechecks regularly |
| You are entitled | an active subscription to that template's product |
| You are reachable | your deployment has been in touch within the last day |
If you stop appearing
Almost always one of these:
- You moved. Verification does not transfer to a new address — it re-confirms on the next check, and you are unlisted until it does.
- You went quiet. A deployment that stops checking in drops off within a few hours.
- Your entitlement lapsed. Same subscription that gates the spec.
Nothing needs approving by hand, so there is nobody to chase. Fix the cause and you reappear on the next check.
Your deployment must be reachable from the public internet at the address you published, over HTTPS. An address that only resolves inside your network cannot be confirmed, and will never be listed.