Using Templates
Going from a template to a live app takes under two minutes. You get your own copy of the whole project — code, database, endpoints, auth — ready to edit and deploy.
Starting from a starter template
Starter templates are the default entry point when you create a new project.
Click New Project
From your organization dashboard, click New Project (or use the onboarding flow if this is your first project).
Pick a starter
Choose between Landing + admin, App with sign up, Private app, or Blank. The description tells you what each includes.
Name your project
Enter a name. DYPAI derives a unique slug and provisions the backend automatically.
Done
Your project is live. The frontend is deployed at your-project.dypai.app, and the backend is ready to accept calls.
Starting from a marketplace template
Browse the marketplace
Go to dypai.ai/marketplace or the Marketplace tab in your organization. Filter by category, search by keyword, or sort by popularity.
Open a template
Click any template to see its full description, gallery, features, and live demo.
Click Deploy
Confirm your target organization and give your copy a name. For paid templates, you'll go through checkout first.
Wait for provisioning
DYPAI creates a new project, clones the repo into it, creates the database schema, and registers the endpoints. Takes about a minute.
Customize
Open your new project's dashboard. Rename things, change copy, add your own tables, plug in your own branding.
After installing
Your new project is a normal DYPAI project — nothing is locked, nothing is read-only. You can:
- Edit the frontend code (from your IDE or the dashboard)
- Modify tables and endpoints
- Add or remove integrations
- Connect a custom domain
- Publish it as a new template if you make substantial changes
Integration credentials
Many templates use external services — Stripe for payments, Resend for email, OpenAI for AI agents, Telegram for bots. The template includes the code, but not the keys.
After installing, go to Credentials → Add new in your dashboard and add your own keys for any integration the template uses. The template's README usually lists what's needed.
Never ship with example keys
Templates ship with placeholder credentials removed. If something isn't working, check the Credentials tab — a missing key is the usual cause.
Starting from a template with your AI agent
If you have the DYPAI MCP installed, you can skip the marketplace UI entirely. Just tell your AI assistant:
"Create a new project using the clinic management template"
"Find me a template for a CRM and deploy it"
It calls search_project_templates to find matches and create_project(template_slug=...) to deploy.
Template versioning
Marketplace templates have a version field. When the author publishes an update:
- New installs get the latest version
- Existing projects are not affected — your clone is frozen at the version you installed
This means template updates never break your running app. If you want the newer version, the template author's release notes will explain what changed, and you can manually pull changes from their public repo.
Free vs paid
- Free templates deploy instantly — no checkout.
- Paid templates ask for payment first. Once paid, the deploy flow is identical to free templates. You own the clone permanently.
Paid templates are useful when you need production-quality code and want the author's time invested in supporting and improving the template.
Limits
| Templates per organization | Unlimited |
| Starter templates | Always free |
| Marketplace templates | Cost varies — check the template page |
| Installation time | ~1–2 minutes |