Skip to content

Creating Your First Project

Create a project, configure environments, and set context for reliable autonomous runs.

A Project is the top-level container in Certyn. It groups your environments, tests, processes, runs, issues, and wiki context for a single application.

First-time onboarding (automatic)

On your first sign-in, Certyn automatically creates:

  • a starter project (for example: "My Project")
  • a default Production environment (with a placeholder base URL)
  • the standard processes: App Explorer, Smoke Suite, Regression Suite

Then Certyn shows an onboarding wizard where you:

  • set the environment base URL for where Certyn should test
  • optionally store login credentials as environment variables (LOGIN_USERNAME, LOGIN_PASSWORD)
  • watch live testing so you can confirm the agent can reach and use your app

When the wizard completes, Certyn starts the App Explorer baseline run and turns on the standard suites so they run on schedule/triggers.

Configure Environments

Environments tell Certyn where to run sessions and what variables/models apply.

Open the environment selector in the header and click Manage Environments.

Most teams create environments like:

  • staging (recommended as default)
  • production (already created by default)

For each environment, set:

  • Base URL
  • Variables (optional): credentials and test data keys like LOGIN_USERNAME, LOGIN_PASSWORD
  • Model (optional): which model to use for sessions in this environment

Public access required

Agent sessions run in remote containers. Your environment URL must be reachable from the internet (or from wherever you host Certyn).

Create additional projects (optional)

If you operate multiple apps, create a project per deployable app.

In the dashboard, open the project switcher in the sidebar header and click Projects to create more projects.

Add Wiki context

Open Wiki and fill in:

  • Overview: primary users, critical flows, out of scope
  • Rules: stable statements that must always be true

This reduces ambiguity and improves both explorer decisions and issue quality.

Collaborators (if enabled)

Certyn supports project collaborators with roles like owner, editor, and viewer. Depending on your deployment, the UI for inviting collaborators may be enabled under Projects.

Not a replacement for Jira/Linear/GitHub Issues

Certyn can integrate with external trackers, but your external tracker remains the source of truth for ownership and status.

What's next?