Skip to main content

Choose your path

Start with the path that matches what you are trying to do. You can switch later, because the console and your coding agent work on the same project.

I built an app and want it running​

Use the web console.

  1. Open passo.build and sign in.
  2. Create a project and connect the repository.
  3. Answer the product questions. That produces the build plan.
  4. Work through the security review, the architecture and the cloud comparison.
  5. Confirm the release into your account, or a managed one.

Read next: Use the web console.

I want my coding agent to do the build work​

Use the console to connect the repository and define the plan, then let your agent execute it.

  1. Connect your coding agent. One command, then a browser sign-in.
  2. Ask the agent to pick your project and take the next task.
  3. The agent does the work, reports progress with evidence and hands the task back. passo.build decides whether the evidence is enough.

Read next: Use passo.build inside your coding agent.

I have an idea but no code yet​

Start in the console and describe the product instead of connecting a repository. passo.build writes the plan and your agent builds from it. The stages after that are the same.

I am reviewing whether the result is safe to ship​

Read What counts as evidence and the security overview. The short version: the public app, the private APIs, the database, storage, jobs, auth and secrets each need a clear home and proof that it is in place before release.