Build deployable apps faster
with AI-ready
module contracts
PloyKit uses module contracts to constrain boundaries while host capabilities carry common product logic. AI only needs to focus on the current module to generate pages, APIs, jobs, and data structures with less context.
01import { defineModule } from '@ploykit/runtime';0203export default defineModule({04 id: 'cms',05 version: '1.0.0',06 permissions: ['read:posts', 'write:posts'],07 routes: [08 { method: 'get', path: '/posts', handler: 'listPosts' },09 { method: 'post', path: '/posts', handler: 'createPost' },10 ],11 jobs: [{ name: 'publish-render', schedule: '0 9 * * *' }],12 events: ['post.created', 'post.updated'],13});A modern web stack works with the module runtime, taking products from local development to deployable releases.
Modular extension
Pages, APIs, jobs, and data plug in as modules with clearer product boundaries.
Built-in capabilities
Auth, dashboard, files, billing, notifications, and workers are available by default.
Easy deployment
Local development, module composition, runtime storage, and deployment stay aligned.
Open and controllable
Code, modules, and product pages are versioned in-repo for review and extension.
Why PloyKit works for AI-assisted development
Contract-first modules
Pages, APIs, data, jobs, permissions, and events live in one declaration, so AI does not have to guess the project shape.
Smaller context
Each task can focus on the current module and contract, reducing global code reading, shortening prompts, and stabilizing output.
Clear delivery path
Generated modules plug into host capabilities, then move through the same runtime path for validation and deployment.
Host capabilities are ready, modules only add business logic
Auth, routing, data, files, jobs, events, and diagnostics are handled by the host. Modules declare what they need through contracts, then run, trace, and deploy through one runtime.
Data & schema
Declare data models, migrations, and access boundaries while the host handles storage and runtime mapping.
Pages & routes
Modules declare public, user-center, and admin entries, then the host mounts them consistently.
Jobs & events
Scheduled jobs, webhooks, business events, and result tracking flow through the shared runtime.
Files & artifacts
Uploads, storage, permissions, and module-generated files are managed by the host.
Service connectors
AI, email, payments, and external APIs connect to modules as host capabilities.
Module Doctor
Scan contracts, permissions, routes, and dependencies to catch integration risks early.
Start with one module and compose a complete app
Declare one module, attach the host capabilities it needs, then compose CMS, CRM, commerce, or internal tools around the use case.
Declare pages, APIs, schema, jobs, and permissions through the contract.
Choose the auth, workspace, file, billing, or event capabilities it needs.
Compose CMS, CRM, commerce, or internal tools and launch.
CMS
Content models, editorial flows, publishing.
Shop
Catalogs, orders, payments, files.
CRM
Customers, leads, activities, pipelines.
Workflow
Connect apps, jobs, and tasks.
Automation
Jobs, triggers, and workflows.
Reports
Dashboards, analytics, exports.
Start with a module contract and let the host run the product.
Read the docs, inspect the module contract, and plug your business capability into PloyKit. Common capabilities stay in the host while modules focus on product logic.