> For the complete documentation index, see [llms.txt](https://govplane.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://govplane.gitbook.io/docs/documentation/govplane-cloud/quickstart.md).

# Quickstart

Govplane Cloud is a flexible governance platform that can be configured in many different ways depending on your architecture and operational needs.

However, in this guide, we’ll walk through the simplest possible implementation so you can start testing Govplane Cloud in just a few minutes.

Let’s get started.

***

### 1. Create Your Account

1. Go to: <https://app.govplane.com/signup>
2. Register your account.
3. Verify your email address.

***

### 2. Complete Onboarding

After email verification, you’ll be guided through the onboarding process.

You will need to:

* Provide an organization name
* Create your first project
* Select a plan tier

{% hint style="info" %}
**Trial Information**

* A 15-day free trial begins once you provide a valid payment method.
* You can cancel anytime before the trial ends and you will not be charged.
  {% endhint %}

Once checkout is completed successfully, you will be redirected back to the application.

***

### 3. Access Your Organization

1. Go to the Organizations page.
2. Select your newly created organization.
3. Open your first project from:
   * The Project list, or
   * The Projects section in the sidebar.

***

### 4. Create Your First Policy

Inside your project:

1. Click Create Policy
2. Define:
   * Policy Key (unique identifier used in runtime)
   * Friendly Name
   * Description
   * Default Effect (Allow or Deny)
3. Add at least one rule

{% hint style="info" %}
**Important**

Enable the option:

> “Activate policy version upon creation”

This activates version v1 immediately and instructs the runtime bundle builder to generate a bundle containing your policy.<br>

**If you forget to activate it:**

* Go to the policy details page
* Manually activate version v1
  {% endhint %}

***

### 5. Connect Your Project (Runtime Setup)

To allow your application to evaluate policies:

1. Go to the Connect section.
2. Create a new Runtime Key.
3. Copy the Runtime Endpoint URL and the generated key. You will use them to configure the SDK below.

{% hint style="warning" %}
The Runtime Key is displayed only once.

Copy it immediately and store it securely (e.g., environment variable manager, secrets vault).
{% endhint %}

***

### 6. Continue with the SDK of your choice

From this point onwards, you will need to implement it in your runtime, using one of the available SDKs:

[Node.js](/docs/documentation/getting-started/quickstart-1/node.js.md)

***

### What’s Next?

Once your first evaluation works, you can:

* Add more complex rules
* Introduce contextual input
* Create multiple policies
* Integrate Govplane into your CI/CD workflows
* Move to production environments

Govplane is designed to scale from simple checks to enterprise-grade governance orchestration.

You’re now ready to build with confidence.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://govplane.gitbook.io/docs/documentation/govplane-cloud/quickstart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.