Platform Limits
Creght is a platform for building websites with AI: you describe what you need, and the platform generates, hosts, and publishes it. It is not a general-purpose cloud, and it does not run arbitrary programs.
Here is where the current version stops: what it does, what it does not, and where the quotas live.
Supported today
An AI-generated site is a React app running on Creght: server-rendered, with the database, cache, and backend functions all managed by the platform. Here is what it does today.
- Generate a multi-page site from a description, then edit by chat
- File routing,
getServerSideProps,metadata - Crawlers and AI agents receive complete HTML
- Multilingual sites
- Structured content: articles, products, cases
- Site forms with email notifications
- CDN for images and video
- Business logic for bookings, signups, leads, approvals
- No instance to buy, no connection string, no backups to run
- Third-party APIs and LLMs, credentials in env vars
- Email, Google, and GitHub login
- Alipay desktop web payments
- No sessions or callbacks to implement
- Mainland China / Hong Kong / US access nodes
- Custom domains, automatic HTTPS, ICP filing
- SEO, sitemap, robots,
llms.txt, and.mdfor any page - Visit analytics and custom events
- Preview first; production moves only on publish
- One-click rollback, backups, multi-user editing
- Export built HTML/CSS/JS and host it anywhere
- Take the React project source through the CLI
The export covers the frontend. Content management, backend functions, login, and payments depend on the Creght runtime and do not travel with the exported files.
Not supported yet
Quotas
Content entries, forms, storage, traffic, collaborators, and version history days vary by plan; see the pricing page for exact numbers.
What AI cannot do for you
- It does not know your business factsPrices, credentials, cases, and contact details are placeholders to verify before launch.
- Replication is not pixel-perfectA reference site or screenshot gets you close, especially where animation is complex.
- The same prompt gives different resultsSay what to change instead of repeating the instruction.
- Some steps are yoursDomain verification, ICP filing, payment approval, third-party authorizations.
- Results need reviewCheck mobile, submit each form once for real, read every locale.
Working around a limit
- Look for a third-party embed first: video hosting, live chat, calendar booking, email marketing, streaming.
- To reach your own systems (ERP, CRM, inventory): have AI call their API from a backend function, with credentials in environment variables.
- For interactions AI cannot generate: pull the source with the CLI, edit it with the Creght Skill, push it back.
- When you hit a quota: upgrade the plan, and contact support if that is still not enough.
To spend fewer credits, describe the whole change once instead of guessing in rounds. See the AI credits guide and the prompt writing guide.
This describes the current version, and every release may add capabilities, so the "not supported yet" list should keep shrinking. If your project sits right on a boundary, contact support to check the latest status.
