01Documented

Check compatibility

Websites, frontends, APIs and Docker Compose services can be hosted. Stateless applications and those using external data services have the most direct path. Local persistence requires external backups and tested restoration.

The beta is not suitable for applications that require a contractual availability or recovery guarantee.

02Documented

Review the requirements

Use the V-Decent app-development skill with your coding agent, then prepare a production setup that can be tested on its own:

  • GitHub repository with docker-compose.yaml at the root.
  • Internal ports via expose; no host port mappings or custom networks.
  • Environment variables for secrets and an application /health endpoint.
  • Resource limits appropriate to the selected category and a clear data strategy.
  • Production manifest tested locally without development overrides.
Open the V-Decent app-development skill ↗
03Documented

Request access

The official registration opens on another platform, currently in English, and requires Google or GitHub authentication. Once approved, you receive access to register your application.

Account approval comes before registration and deployment. Permissions depend on your approved account. Already approved? Open App Manager from the platform menu.

Request access ↗
04Documented

Your AI agent sizes the application

Sizing is part of the preparation done by the AI coding agent; developers do not need to run the profiler themselves. Tell the agent how the application will be used so it can size a representative workload.

When Docker and the profiler are available, the agent runs vdecent-size against the local Compose app under representative workload, applies the per-service recommendations and records the result in docs/vdecent-handover.md. The profiler stays in development tooling, outside the production image.

  • If the profiler cannot run or a representative workload is unavailable, the agent estimates with the V3.2 VRU method and records the assumptions.
  • Review the agent’s recommended tier and per-service limits in the handover, then confirm the registration details in App Manager. Already healthy apps only need re-sizing when their workload changes.
Read the V3.2 agent sizing instructions ↗Explore all guides and tools →
05Documented

Follow your first deployment

Once approved, register the GitHub repository in App Manager. Confirm the Compose analysis and selected tier, set the domain and environment variables, then start deployment. Follow the logs and wait for the public health check to pass.

Have the application name and URL, purpose and stack, exposed service and port, data and backup needs, repository visibility and branch, and developer group and GitHub owner ready for the registration form.

If something fails, inspect the logs and use the support channels available to your account. A successful deployment does not replace a plan to protect your data.

Read the development guide ↗

Ready to begin?

Request access through the official registration, in English, using Google or GitHub. Access is subject to review and approval.

Request access ↗