Getting Started
Welcome to CodeSCE — a marketplace for ready-to-use code modules. As a buyer, you browse the catalog, purchase the modules you need, configure them through a form, and drop them straight into your own project.
What you can do on CodeSCE
- Discover modules across categories like UI Components, Forms, Dashboards, and more.
- Preview before you buy — every module has a live UI preview, a README, and its configurable options laid out on the module page.
- Buy securely — paid modules are purchased with cryptocurrency (USDT), and ownership is only granted after the payment is verified on-chain.
- Download safely — purchased modules are delivered through short-lived, one-time links, and each ZIP is watermarked to you.
- Configure without touching code — modules expose their settings as a dynamic form.
- Keep what you own — every purchase is recorded permanently under your account.
Account & authentication
CodeSCE uses social sign-in — there are no passwords to manage.
On the sign-in screen you have two options:
- Continue with Google
- Continue with GitHub
Choosing a provider takes you through that provider's standard consent screen. When you return, CodeSCE creates a secure session for you (stored as an auth_token cookie) and, for first-time users, walks you through a short two-step onboarding to set up your profile.
Your email
Your email address is provided by Google or GitHub during sign-in — you never type a password into CodeSCE.
Signing out
Signing out ends your current session on the server, so any active download links immediately stop working. You can sign back in at any time.
Desktop vs Browser
CodeSCE runs in two places, and they share the same account.
| Web | Desktop app | |
|---|---|---|
| Where | Any browser at codesce.com | Native app (Windows/macOS) |
| Sign-in | In the browser tab | Opens your system browser, then returns to the app |
| Best for | Quick browsing and buying | A local workflow for pulling modules into projects |
How desktop sign-in works
For security, the desktop app never asks for your Google or GitHub credentials inside its own window. Instead:
- When you start sign-in, the app opens the auth pages in your default system browser.
- You authenticate with Google or GitHub there, in a normal, trusted browser.
- When it's done, the browser hands your session back to the app through a
codesce://deep link, and the app loads you in — already signed in.
Everything that isn't an auth page (browsing, buying, downloading) happens right inside the desktop app.
Which should I use?
Start in the browser if you just want to explore and buy. Install the desktop app when you want the smoothest local workflow for integrating modules. See Desktop App for details.