From a requirement
to project source.
Start with a customer table. Describe the records and fields, refine the same project through conversation, then take the complete source into your own development environment.
For individual developers and small teams · Verify and deploy locally
“Manage customers with a name, status, notes, and a priority flag.”
Organize the requirement into an independent module and a complete source snapshot.
customer-project.zipSpend less time on setup, more on your business.
Turn a rough idea into specific requirements
Define records, fields, choices, search, and actions. Clarify missing details before continuing with generation.
Keep improving the same project
Keep the conversation and versions together. Start with customer management, then add a priority flag in the next iteration.
Take the source to your own team
Download the complete project, inspect and run it locally, and continue development within your existing workflow.
Five steps to your first project.
You bring the requirements. The platform organizes a plan and generates source. Check your personal account and model before starting.
Sign in and check your API account
Use GitHub or another enabled sign-in method. Check account readiness and credit under My API account, then select an available model in the assistant.
Star trials follow the campaign rules and recorded receipts. Signing in does not guarantee credit.
Create a project with specific requirements
Name the project and describe its records, fields, choices, and search behavior. Copy an example below and adapt it to your business.
Save requirements stores a draft. Create and generate starts a model call.
Review and refine the same project
Answer clarification questions before continuing. Add a field or an independent module in the same conversation; a successful build creates a new source version.
Prompt optimization is optional. Adoption remains editable; optimization and generation are billed separately.
Download the ZIP for that version
Check the revision in the reply or artifact list, then download the complete source for that version. Save the versions you need on your own device.
Downloads expire. Check the date shown in the platform; pinning a version does not extend its download availability.
Verify and run using the project guide
Read the included getting-started instructions. Follow the open-source mss-boot-admin documentation to prepare your development environment, install dependencies, and verify the app. Your team can continue developing it.
You need a development environment and any required dependency access. Generated source has not been deployed for you.
Begin with one clear, small requirement.
Choose an example and adapt it. This page only displays text; it does not create projects or call a model.
Create a customer module with create, read, update, delete, and export. Name is required searchable text; status is one enum with enabled and disabled values and matching labels, with filtering. Notes are optional text. Priority customer is a boolean. Duplicate names are allowed. Do not add relationships or workflows.
Create an equipment register with create, read, update, delete, and export. Equipment name is required searchable text. Model and location are optional text. In use is a filterable boolean. Duplicate names are allowed. Do not add dates, numeric fields, relationships, or approvals.
Create an issue record module with create, read, update, delete, and export. Title is required searchable text; description is optional text. Status is one enum with open and closed values and matching labels, with filtering. Needs attention is a boolean. Duplicate titles are allowed. Do not add user relationships, attachments, or automated workflows.
Check that the project fits.
Supported today
- 1–4 independent modules, 1–12 fields per module
- Text, booleans, and at most one enum per module
- Lists, forms, details, search, filters, and export
- Complete source, specifications, permission migrations, and test files
Requires separate development
- Relationships, complex numeric or date fields, uploads
- Approvals, workflows, and external integrations
- Tenant or row-level isolation within the generated app
- Automatic deployment, arbitrary code execution, database upgrades
Each module needs a meaningful searchable text field. Platform projects are owner-only; users with module access in the downloaded app share that module’s data.
What to do when you get stuck.
Can I prepare requirements before my account is ready?
Save a draft, then check My API account. Follow the displayed instructions. Once ready, return to the original project and explicitly send the request.
Should I generate again after a timeout?
Check the original request in the same project first. Avoid repeated sends or starting a new project. An unknown result does not mean the model did no work or incurred no cost.
Can I deploy the download immediately?
Read the project’s getting-started guide, prepare your environment using the open-source documentation, and complete verification and business acceptance checks before deployment. Each ZIP is a complete snapshot, not a database upgrade package.
What if downloading or local installation fails?
Keep the project and version IDs and the error message, then contact the platform administrator. Follow the open-source documentation for dependency permissions. Do not pay for another generation to troubleshoot these issues, or send credentials.
Can I use this without local development experience?
You can organize simple requirements, but running the source still needs tools and development experience. Work with a developer for installation, verification, and deployment. One-click hosting is not currently provided.
Start with a business table you know.
Describe the fields, choices, and search behavior, then open the assistant.