From the first deployment onward
Use Proto’s built-in integration or connect another skill-capable coding agent. Deploy a project, inspect logs, configure environment variables, ship an update, and restore an available earlier deployment. Your account’s approved capabilities determine which builds and workloads can run. Read the hosting scope before choosing a project architecture.
Useful starting points, openly maintained
The template collection and Design Skill Library help when you want a considered starting point. Their public source repositories are separate from the hosting dashboard codebase. Contributors submit work for review; the published catalog links to downloadable, versioned files. A preview may demonstrate a visual concept, so each project still needs its own implementation and verification.
Practical publishing
Our blog and deployment guides explain workflows, tradeoffs, and limits. Articles use the build.host organization as their author when they are maintained as product documentation. Sample content is identified, and external guidance is linked where relevant. Updates should reflect substantive changes, with working source and accurate publication dates.
After you publish
To understand traffic from server logs, explore knockstat. If you also manage your own servers, Picket provides host threat-hunting across an SSH fleet. These are separate tools to evaluate for your infrastructure and access needs.
Serious business apps
For business data, roles, forms, and workflows, use ERP.AI. Download Proto and describe what you want to build. Visual design, hosting, and the business behavior of an application are related decisions; use the right capabilities for each.