Start with your agent

Open your project in a coding agent with terminal access, then paste this prompt:

Read https://jollop.run/llms.txt and help me deploy this project to Jollop. Help me sign in if needed, verify the app, and give me a secure link.

Your agent reads the public setup instructions, checks your access, deploys the selected project, and verifies the result. You need a Jollop account or an existing credential. If registration is closed, arrange account access with the operator before deploying. Check the sign-in page for the available options.

Use the tools you already have

If jollop is installed, the agent can use the CLI. Before signing in, it checks the server’s /auth/config: when email delivery is log, emailed codes are unavailable. Existing users can sign in with their password:

SSC_SERVER=https://app.jollop.run jollop login --password
SSC_SERVER=https://app.jollop.run jollop deploy .

When email delivery is configured, jollop login without --password also supports an emailed code.

If you have configured Jollop MCP, your agent can use its deploy tool instead. Without either client, the setup instructions describe the same authenticated HTTPS upload API. That route does not require a CLI installation or access to the platform’s source repository.

What the prompt does

The agent deploys the project you choose, follows the build output, and checks the resulting page or API. Keep your dependency manifests and application assets in the project. Jollop uses the code’s dependencies and observed behavior to work out its runtime and backing services, including Postgres.

The example on the homepage uses a React frontend, Django backend, and Postgres database. It illustrates the workflow; your app still needs to include its dependencies and use the environment settings supplied by the platform. See backing services.

New apps use secure-link access by default. The starter prompt asks your agent to create a secure link, use it to verify the app, and return it to you. Anyone holding that link can open the app, so keep it private unless you want to share it. Making an app public is a separate choice. See sharing.