Deliberate choices. Know what you are building on.
These are the tools behind the application you are using. Their integration code ships in the source ZIP. You provide your own accounts, credentials and domains to run your copy, and build any product-specific logic.
Six choices to get comfortable with.
These choices shape setup, development, and operation. Here is how YeetCode uses each service, and what that means for you.
Secrets & environment setup
1Password
Environment templates reference secrets in 1Password. The CLI and Make commands generate local app files and push configured secrets to Convex.
What you are choosing
Use a 1Password account and the CLI for the included setup workflow. If your team uses another secret manager, you will need to adapt that workflow.
Data & backend logic
Convex
The connected app shares a TypeScript backend for data, queries, mutations, and durable workflows. Convex subscriptions keep the UI connected to changing data.
What you are choosing
Create and configure your own Convex deployments. Your data model and backend logic use Convex APIs, so moving to another backend requires code and data migration work.
App hosting & deployment
Cloudflare
The Next.js apps include a deployment path to Cloudflare Workers through OpenNext and Wrangler. GitHub Actions handles the configured release deployments.
What you are choosing
Provide a Cloudflare account and deployment credentials. Check your app against the Workers runtime. Another host needs its own deployment configuration and validation.
Identity & sign-in
Clerk
Clerk provides sign-in and session handling for the connected app. The integration connects identity to Convex and synchronizes user information with the backend.
What you are choosing
Configure your own Clerk application and credentials. Another identity provider means adapting authentication, user synchronization, and access checks.
Checkout & product access
Polar
Polar powers checkout and billing. Billing refresh reads orders from Polar, stores confirmed purchases and grants access to the selected source release.
What you are choosing
Set up your own Polar organization and products. This app refreshes billing when a customer returns from checkout or opens their library; it does not require Polar webhooks. A different payment provider needs changes to checkout, billing events, and purchase access logic.
Product email
Resend
Convex workflows send product emails through Resend. Shared React Email templates define the messages and branding in editable source.
What you are choosing
Configure a sending domain and Resend credentials. Another email provider needs a delivery integration and checks that product events still send the right messages.
One consistent way to build.
The service choices sit on a shared development toolchain. These are the main tools you will work with in the source.
Application & interface
App Router pages form the applications. Strict TypeScript connects the code. Shared UI primitives, styles, and prop-driven marketing blocks keep the interface consistent.
State, themes & motion
The connected app uses shared providers for queries, light and dark themes, and motion. Interactive components build on these foundations.
Development & checks
Bun installs dependencies, runs scripts, and tests the code. Turborepo coordinates workspace tasks. Biome handles formatting, linting, and import organization.
Email & releases
React Email keeps email templates in the repository. GitHub Actions runs checks and release workflows. release-please manages repository versions and one shared changelog.
Choose the foundation with open eyes.
You control the source and can change it. Replacing a service is engineering work: integrations, data, and deployment may all need changes. It is not a settings switch.
Starting with a prototype? The lightweight app does not need Clerk, Convex, or Polar. The connected app is the starting point for the service integrations shown here.
A good fit if you are comfortable with:
- Building with these tools and learning their workflows.
- Owning and configuring the service accounts your product needs.
- Paying hosting and service usage fees separately from the source purchase.
- Maintaining your product and reviewing the selected release before buying.
Your requirements deserve the right setup.
Prefer another backend, payment provider, host, or secret manager? LYEMAC is the parent company behind YeetCode. Tell us what you want to build and which tools your team needs, and we can discuss a custom approach.
Custom implementation is a separate conversation and scope. It is not included in a YeetCode source snapshot.