User / Client
Create projects, use Code, Learn and AI Builder, manage domains, buy templates, review billing and deploy completed projects.
TRYNLE DOCUMENTATION
Build. Connect. Launch. Manage.
Everything you need to understand the TRYNLE platform, from creating a project and working with code to choosing a domain, deploying a confirmed version and managing the live lifecycle.
01ProjectCreate
02BuildCode / AI
03PreviewConfirm
04DomainConnect
05DeployLive
Start with the workspace that matches your role.
TRYNLE supports User / Client and Developer workspaces. Registration asks which workspace you want to join so the platform can route you to the tools relevant to your work.
Developer
Create projects and templates, work with source files and builds, submit templates for approval, publish approved marketplace assets and manage earnings.
Create an account
- Select Register.
- Choose User / Client or Developer.
- Enter your name, email and password.
- Confirm the password and create the account.
- Continue into the workspace for your selected role.
One workspace for the complete customer journey.
The Client Workspace brings projects, Code, Learn, AI Builder, domains, templates, billing and account management together.
Build first. Choose the domain when you are ready to go live.
A domain is not required to begin development. Finish the project, review the generated output and then choose the domain path at the go-live stage.
01
Create
Define the project name, goal, type and required features.
02
Build
Assemble the project and configure its structure.
03
Code
Review or work with the generated source files.
04
Generate
Create a versioned project artifact.
05
Preview
Check desktop, tablet, mobile, links, forms and interactions.
06
Confirm
Approve the version before moving to go-live configuration.
07
Connect Domain
Use a TRYNLE domain, external domain or search for a new one.
08
Deploy
Publish the confirmed version to its deployment target.
09
Live
Open the release using its live URL and connected domain.
Move from a brief to a real, reviewable project.
Code Workspace
Open a generated version, inspect the file tree and review source such as index.html, style.css, app.js, JSON configuration and assets. Preview and deployment stay connected to the project version.
AI Builder
Describe the website or digital project you want. TRYNLE can structure the request into a project goal, pages, routes, features, environment requirements and suggested testing. Review the generated plan before continuing.
Choose how you want your project to reach the web.
When your project is confirmed, TRYNLE gives you three clear domain choices.
TRYNLE domain you already own
Select a registered TRYNLE domain from the project go-live screen and connect it to the project.
Open Domains →Domain from another provider
Enter the external domain, add the ownership-verification DNS record supplied by TRYNLE and run verification before deployment.
Connect a domain →No domain yet
Search for a domain through TRYNLE, register an available name, return to the project and connect it.
Search domains →External domains require ownership verification.
TRYNLE can issue a unique TXT verification challenge. Add the exact record at your current registrar, wait for DNS propagation and select Verify. An unverified external domain cannot be treated as ready for deployment.
Common DNS records
Depending on the deployment configuration, TRYNLE may provide A, AAAA, CNAME or TXT records. Always use the exact values shown for your domain and project.
Publish the exact version you reviewed.
Deployment is the final operational step after the project has been generated, previewed and confirmed.
01GenerateCreate a project artifact.
02ValidateCheck the generated output.
03DomainConnect and verify when required.
04DeployPublish the selected version.
05LiveOpen the release URL.
Pending Request acceptedBuilding Artifact preparedDeploying Files being publishedLive Release completedFailed Review the deployment details
Buy ready-made templates or publish your own as a developer.
Clients
Browse approved templates, open live previews, review template information, purchase eligible assets and download purchased templates.
Developers
Create a template, test it, submit it for administrative approval and publish it when approved. Marketplace sales feed the configured developer earnings workflow.
Create→Build→Test→Submit→Admin Review→Approved→Published
Keep financial records connected to their transactions.
Billing can include project charges, template purchases, domain registration, renewals, payments, invoices and developer payouts.
Global currency
Administrators can choose the platform's default currency from Admin → Settings → Currency. Supported workflows format new pricing and financial records using the configured currency.
Historical transactions
Existing financial records retain their recorded transaction currency instead of being silently rewritten when the platform default changes.
Build marketplace assets and manage technical releases.
Developer tools can include projects, templates, builds, code, deployments, API keys, webhooks, diagnostics, earnings and payout workflows.
Operate the platform from one command center.
The Admin Console provides centralized controls for users, projects, templates, domains, commerce, payment gateways, payouts, frontend content, registry operations, support, security, jobs, health, audit and settings.
Control Center
Overview · Users · Projects · Templates · Domains
Commerce
Invoices · Payments · Payment Gateways · Developer Payouts
Platform
Frontend Content · TLD Registry · Support · Security · Jobs & Queue · Health · Audit
Settings
Site identity · Support email · Language · Currency · Maintenance and platform configuration
Security controls are part of the workflow.
Password hashing CSRF protection Role-based access Secure reset tokens Domain ownership checks Audit logging
Never share passwords, password-reset links, API secrets or private credentials. When reporting an issue, provide the error and relevant project information without exposing credentials.
Questions before you start?
Do I need a domain before building?
No. Build, generate and preview your project first. Choose a domain when you are ready to go live.
Can I use a domain purchased somewhere else?
Yes. Connect the external domain and complete the ownership-verification step before deployment.
Can I buy a domain through TRYNLE?
Yes. Use the domain search and registration workflow, then return to your project and connect the registered domain.
Can developers sell templates?
Yes. Developers can create and submit templates for administrative approval. Approved assets can be published in the marketplace.
Does AI automatically deploy my website?
No. AI assists with planning and project generation. Review, preview, confirm, connect a domain and deploy through the normal release workflow.
Does changing the platform currency rewrite old transactions?
No. Historical transaction records should retain their original recorded transaction currency.
Quick checks when something does not move forward.
Project won't deploy
Confirm that a generated version exists, the artifact is valid, a usable domain is connected and any external domain has been verified.
External domain won't verify
Check the TXT hostname and value exactly, wait for DNS propagation and run verification again.
Domain isn't available
If you don't own a domain, search and register one through TRYNLE. If you already own one elsewhere, use Connect Existing Domain.
Password reset email missing
Check spam/junk, confirm the email address and verify the platform mail/SMTP configuration.