How it works
How it works
Last updated: January 1, 2026
From checkout to your first deploy — what happens after you buy Uno, step by step.
One-time purchase
You pay once through Stripe Checkout. Access is delivered immediately after payment is confirmed.
Magic-link sign-in
Your welcome email signs you straight into the customer portal — no password to set up first.
Everything in one place
Downloads, billing, and the full documentation live in your customer portal.
Choose your package and pay
Pick a package on the pricing page and click the buy button. You are taken to Stripe Checkout, where the price, currency, and what your purchase includes are shown before you pay.
Before paying you accept the Terms of Service and confirm immediate delivery of the digital content together with the loss of the statutory 14-day withdrawal right. Once access is granted, the sale is final — see section 10 of the Terms.
Check your inbox
Right after a successful payment we provision your account automatically and send a welcome email to the address you used at checkout. It confirms your purchase and contains a magic sign-in link.
If the email does not arrive within a few minutes, check your spam folder, then write to rafal@piekara.me and we will sort it out.
Sign in with the magic link
Click the magic link in the welcome email and you are signed in — no password required. You can add a password or another sign-in method later in your account settings.
The link is personal and time-limited. If it expires, request a fresh one from the sign-in page using the same email address.
Your customer portal
After signing in you land in the customer portal. It shows your purchase — lifetime access to the version you bought, with new releases for 12 months from the purchase date.
The Manage billing button opens the Stripe customer portal for invoices and billing details, and the documentation card takes you to the full docs.
Get the code and start building
Your copy of the codebase is delivered through the customer portal. Follow the getting-started guide in the documentation: bin/setup installs dependencies, prepares the databases, and starts the dev server.
The full documentation — architecture, feature deep dives, deployment — lives at /docs and is available to you as a customer.
Updates
New releases published during your 12-month update window are delivered the same way — pick them up whenever you like. Release notes call out breaking changes.
When the update window ends, everything you already received keeps working and stays licensed; you simply stop receiving new releases. Details are in the Support & Updates Policy.
Need help?
Write to rafal@piekara.me about defects in unmodified template code, unclear documentation, or setup problems. The full support scope is described in the Support & Updates Policy.
Security reports get priority — start your subject line with SECURITY.