# How to Collaborate on PipeOps Projects
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

Effective collaboration is the backbone of any successful technical project. Whether you're managing a small development team or coordinating across multiple departments, PipeOps provides the tools you need to work with different users. This guide will walk you through how to set up and manage collaborative projects effectively.


\
&nbsp;

## PipeOps Workspaces


Think of workspaces as separate organizations or units within PipeOps.
A workspace is a container for projects, teams, servers, and integrations. This is particularly powerful for:


- **Multi-client agencies:** Separate workspace for each client
- **Enterprise organizations:** Different workspaces for different business units
- **Project-based companies:** Dedicated workspace per major project
- **Personal vs. professional separation:** Keep your side projects separate from work


You can switch between them using the Workspace tab in the top nav.

![Workspace Nav](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Workspace_Nav_6c4a785165.png)



\
&nbsp;

### Setting Up Workspaces

Your PipeOps account comes with a default workspace. To create a new one:

- Click on the workspace tab in the top navbar

![Workspace Tab](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Workspace_tab_fe5345593e.png)


- Select "Create New Workspace" from the dropdown

![Workspace Name](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/New_Workspace_493e07149b.png)





- Enter a workspace name and click Create.

![Workspace Name](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Create_Workspace_9f4a421e47.png)



\
&nbsp;

## Setting Up Teams within Workspaces

To begin collaborating on PipeOps, you need to set up your team within your workspace. Here’s how to do that:

### Creating a Team

- Click the ‘’New” button on the top right corner of your dashboard and select “Team” from the dropdown menu.  Alternatively, click on the profile icon, and select “Teams” from the dropdown.

![Create Team](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Create_Team_921c043cc7.png)

![Create Team](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Create_Teams_eaeb4ada8f.png)



- On the teams page, click the "+ New team" button at the top-right of your screen. If you haven't created any teams yet, a "+ create a new team" button will be at the center of the page as well.

![New Team](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/New_Team_1c32004c12.png)


Fill in your team details:

![New Team](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Team_Details_f92c33b75f.png)

- Team Name: Give your team a name.


- Assign Resources: Select the resources you want the team to access, such as  servers, projects, and add-ons.

- Click "Create Team" to complete your setup.


\
&nbsp;

## Inviting Team Members

Adding a member to your team is quick. You can use the "Invite Team Member" section during team creation. Alternatively, navigate to the desired team and click on the "+" icon.

![New Member](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Team_Details_f92c33b75f.png)

![New Member](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Add_Member_ed6152132f.png)

A user-friendly form will appear, where you’ll provide the following information:

![ Member Details](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Member_Access_dd5017697f.png)


- Team member's email address


- Select user role (guest, member, or admin):

    Guest - this member gets read access to all resources

    Member - read and write access to all resources in the team

    Admin - read and write access to all resources in the team. The admin can also add or remove team members. 


![ Member Access](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/User_Roles_bd0bd4b76e.png)

- Assign access and permission to specific resources 

This section allows you to state the level of access each member has to each resource in your team. For each resource you select, you can choose if the member can view, edit, or delete.


![ Resource Access](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Resource_Permission_23414be024.png)


![ Member Details](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Member_Access_dd5017697f.png)

- Click the “Add invite” button to send the invitation. 

    Team members will receive an email invitation to join the team.
    



\
&nbsp;


## Utilizing Audit Trail

The Audit Trail feature provides a detailed record of all actions performed within a team, ensuring transparency and accountability.

To access the Audit Trail feature:

- Navigate to the "Teams" section. Click on the specific team whose audit logs you wish to view.



- Select the "Audit Trail" tab.

![Audit Trail](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Audit_Trail_b8453e0ea6.png)


The audit trail displays key details such as:


  -   **User:** The name and email address of the user who performed each action.
    
    
   -  **Action:** A description of the event (e.g., permission updates, project creation, member invitations).
    
    
   -  **Timestamp:** The exact time when the action was performed.
    
    
   -   **Search Functionality:** Use the search bar to find specific actions or filter by keywords.


This feature is essential for tracking changes and monitoring user actions within your team.




\
&nbsp;

## Revoke Invites or Remove Members

Imagine a scenario where you send an invite to the wrong email address or a developer leaves your company, and you need to revoke their access. PipeOps makes it easy to manage membership for each team you create.


Navigate to the team the user belongs to and click the “Edit team” tab at the top right of your dashboard. 

This opens a page where you can edit the team details and the list of members, including pending invites. To revoke an invite or delete a member, click the ellipsis close to each email. Doing this opens the option to delete a member or remove the invite.


![Remove member](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Delete_Member_11d8c0c323.png)


![Remove member](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Remove_Invite_0b192d02be.png)

PipeOps equips you with the proper tools for workspace organization and strategic team setup. You can build teams with appropriate access levels for projects or clients. Regular monitoring through audit trails and access management ensures your collaborative environment remains secure and productive as your workload grows.







How to Collaborate on PipeOps Projects

# An Overview of Platform Dashboard and Features

__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

The PipeOps dashboard is your control center for deploying and managing applications.
This guide breaks down the key sections to help you understand what you'll be working with on the platform.

\
&nbsp;
## Dashboard/Projects

________________________________________________________________________________________________________________________
\
&nbsp;

This is your primary landing page when you log in to the console. All your projects are listed here, organized by most recently deployed.

![PipeOps Project](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Projects_5f91678f65.png)

A project in PipeOps is a container for everything related to your application.
From the Projects section, you can access:

-  **Project overview** -  View the general status, resource usage, and recent activity for your project at a glance.

-  **Project history** - See a chronological record of all deployments and configuration changes made to the project.

![Project Detail](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Project_Details_7a02278202.png)

-  **Metrics** -  Monitor resource usage such as CPU, memory, and network to ensure optimal performance.

-  **Logs and events** -  Access detailed logs and event streams to troubleshoot builds and runtime issues.

-  **Worker and Jobs** - Manage background tasks or scheduled cron jobs that are part of your application.

-  **Settings** - Modify environment variables, firewall rules, deployment behavior, domains, build settings, and more.

Project Settings also include options for:

   -  Source control & build settings
    
  -   Networking and firewall rules
    
   -  Environment variables
    
   -  Health checks
    
   -  Storage
    
   -  Domain management

\
&nbsp;

## Servers

________________________________________________________________________________________________________________________
\
&nbsp;

This section displays all servers associated with your account, whether they were created directly on PipeOps Nova servers or your own cloud account.

![Project Server](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Servers_b64483baf9.png)

When you click on a server, you can access:

- **Overview page** – View nodes, current usage, and associated deployments at a glance.

- **Metrics** – Monitor CPU, memory, and network usage in real time.

- **Events** – Track important activities and status changes tied to the server.

- **Nodes** – Inspect individual worker nodes that make up your server.

- **Environments** – Manage deployment environments (e.g., dev, staging, prod) running on the server.

- **Settings** – Customize alert notifications for your cluster resource usage.

![Server Details](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Server_Details_bbb7872038.png)

Servers created on your personal cloud account  will display additional tabs beyond the standard ones. These include Dashboard/Prometheus, Pricing, Update history, and AddOns.




\
&nbsp;

## AddOns

__________________________________________________________________________________________________________________________________________________________
\
&nbsp;

AddOns provide services that can be attached to your projects, such as databases, storage, or monitoring tools. Use this section to provision and manage extra resources that streamline your project.  You can spin them up quickly and connect to your applications. 


![Addons](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Addons_230a6d266e.png)

\
&nbsp;

## Integrations

________________________________________________________________________________________________________________________
\
&nbsp;

This section shows all your connected cloud accounts. Linking your cloud provider accounts here allows PipeOps to provision and manage resources on your behalf.


![Integrations](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Integration_ab3808b5fd.png)

PipeOps currently supports integrations with the following providers:

- AWS (Amazon Web Services)

- Google Cloud Platform (GCP)

- Microsoft Azure

- DigitalOcean

- Huawei Cloud

Once integrated, you can securely create servers and deploy projects in your chosen cloud environment.


\
&nbsp;


## Usage

________________________________________________________________________________________________________________________
\
&nbsp;

![Usage](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Usage_Active_Sub_7daba7fba7.png)

The Usage section helps you keep track of your overall platform consumption. Here, you can:

- Monitor your active subscription and Nova usage.

- View usage breakdown by server, project, and addons.

- Track resource consumption over a selected period.

- Switch or upgrade your subscription plan.



\
&nbsp;


## Workspace

________________________________________________________________________________________________________________________
\
&nbsp;


![Workspace](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Workspace_a14fb31fa0.png)

Think of Workspaces as an organization in PipeOps. Workspaces help you organize teams, projects, and resources within a shared environment. A default workspace is created with your account. However, you can create new ones and effortlessly switch between them.




\
&nbsp;

## Account Settings

________________________________________________________________________________________________________________________
\
&nbsp;



The Account Settings section lets you manage your personal and workspace-level configurations. Everything you need to manage your PipeOps experience is here. You can:

- Update your profile and email preferences.

- Create a team and invite members.

- Change authentication methods or passwords.

- Manage billing, payment methods, and invoices.

![Accounts](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Account_Settings_2ccdbdd97c.png)





\
&nbsp;
### What Next?

Now, you've read enough and are ready to get started. We recommend checking out this resource next:

[Getting Started with PipeOps: From SignUp to First Deployment](https://pipeops.io/resources/guides/24/getting-started-with-pipeops:-from-signup-to-first-deployment)

\
&nbsp;


Overview of Platform Dashboard and Features

# How to Deploy and Connect to RabbitMQ on PipeOps
_________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;


RabbitMQ is an open-source message broker that facilitates reliable communication between services using a queue system. This guide walks you through deploying RabbitMQ on PipeOps, connecting an application to it, and verifying the connection works as expected.


## Deploy RabbitMQ 

- Navigate to your PipeOps dashboard and select AddOns from the sidebar navigation menu.

![Select Addon](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Select_Addon_08463ec29a.png)


- Select RabbitMQ from the addon marketplace. If it’s not immediately visible, use the search bar.

![Search RabbitMQ](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Select_Rabbit_MQ_02d2a1b9dd.png)


- On the RabbitMQ details page, click the Deploy App button at the top right. You’ll be taken to the configuration page.

- Click "Deploy" to launch the RabbitMQ instance. 

![Deploy RabbitMQ](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Deploy_Rabbit_MQ_018e2b7fba.png)

![Deploy RabbitMQ](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Deploy_App_f03abe1541.png)

Wait for the instance to finish provisioning. This usually takes a few seconds.

> **Note**: By default, the RabbitMQ instance starts with minimal CPU and memory to save costs. If you ever feel like your RabbitMQ is slow you can increase the resource (CPU cores and memory) from the AddOn settings tab. 


### Retrieve RabbitMQ Credentials

Once the RabbitMQ instance is running:

- Go to Addons → Select your RabbitMQ instance.

- Click on the Settings  tab and select Environment Variables.

![RabbitMQ Env](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Copy_Rabbit_MQ_Env_6be6babbf8.png)

Copy the values for the following variables:

- ``` RABBITMQ_DEFAULT_USER ```

- ``` RABBITMQ_DEFAULT_PASS ```

![RabbitMQ Env](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Copy_Rabbit_MQ_Env_6be6babbf8.png)

You’ll use these to log in to the RabbitMQ instance.


### Access the RabbitMQ Dashboard 

Click the "View Addon" button to open your RabbitMQ dashboard.



![View RabbitMQ](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/View_Addon_a613afbbd9.png)


![RabbitMQ Login](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Rabbit_MQ_login_2f0d6dd99a.png)


Use the default username and password from the previous step to log in.


You should now see an empty RabbitMQ dashboard with no queues or connections yet.



![View RabbitMQ](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Rabbit_MQ_UI_6a2b56ce44.png)



## Deploy Your Application

Deploy your application that will communicate with RabbitMQ. For this guide, we're deploying a Go project that acts as both a consumer and a publisher for RabbitMQ. 

Upon receiving the RabbitMQ URL, the application connects to it, declares a queue to ensure it exists, creates a consumer to listen for incoming messages, and begins publishing messages to that queue. 


Follow these steps to deploy your application:

- Click the "+ New" button at the top right of your dashboard. Select "Deploy Project" from the dropdown and choose your project type.


![New Project](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Dropdown_Button_59ba06a369.png)



- Next, select your repository and the branch you'll deploy from. Click "Proceed" to continue. Ensure that the application is deployed on the same server as the RabbitMQ instance for internal communication to work.


![Repo and Branch](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Select_Repo_and_Branch_c9ab991796.png)


- On the Project Build Settings page, select your framework and build method. Click "Deploy Project" to start the deployment process.


![Repo and Branch](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Deploy_Project_6b8d267f2b.png)


- If your project deploys successfully, a success modal appears as shown below. 

![Repo and Branch](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Deployed_Successfully_0d28f22c52.png)


## Connect Your App to RabbitMQ

- In your deployed project, navigate to Project Settings and click Environment Variables.

- Add a new variable:

    - Key: RABBITMQ_URL
    
    - Value: ```amqp://{RABBITMQ_DEFAULT_USER}:{RABBITMQ_DEFAULT_PASS}@{addon-name}:5672```

-  Replace {RABBITMQ_DEFAULT_USER}, {RABBITMQ_DEFAULT_PASS}, and {addon-name} with the actual values from your RabbitMQ addon settings. Your addon name is simply your service slug (abc-xy in abc-xy.antqube.io).

  Example: 
  amqp://cb3a72edfs74:a30e6136dcd21d90ad06f3067d50610c@damp-lake:5672


![RabbitMQ Connection](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Connect_Project_a033c3d7fb.png)



- Click **Save** and wait for the deployment to go live.


Once the environment variable is set and the app is redeployed, go back to the RabbitMQ dashboard. You should now see an active connection from your application to RabbitMQ and a queue created.

![RabbitMQ Connection](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Rabbitmq_Connection_eaecaaf7be.png)

![RabbitMQ Queue](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Rabbit_MQ_Queue_8b56fe5d02.png)


👍That's it. You’ve now successfully deployed RabbitMQ and connected to your application. 



Deploy and Connect to RabbitMQ on PipeOps

## How to Enable Firewall Rules on PipeOps 
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;


Firewall rules are essential for controlling network access to and from your deployed applications. By defining clear rules, you can limit access to trusted sources and ensure your applications operate within intended network boundaries. PipeOps provides flexible firewall controls that let you manage both inbound and outbound traffic directly within your project settings.


## Why Firewall Rules Matter
________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;


Firewall rules let you enforce IP policies that define how your application communicates with the outside world. This feature gives you granular control over network access and helps secure your deployment.

You can use firewall rules to:


- Allow only specific IP ranges, helping you meet legal or regulatory requirements.

- Control which ports can communicate with your application.

- Limit access to websites or data to trusted IP addresses.

- Allow outbound access only to specific external services, such as APIs or databases.


\
&nbsp;

## Enabling Firewall Rules

______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

Firewall rules are currently available as a beta feature on PipeOps. Before you can configure firewall rules, you need to enable this feature:


- Go to your PipeOps dashboard.

- In the left sidebar, click Feature Preview.

![Feature Preview](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Feature_Preview_18ccd0d9e7.png)


- Toggle the switch next to Firewall Rules to enable the feature.


![Enable Beta Features](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Enable_Beta_Features_74b6a1a4db.png)


Once enabled, the Firewall Rules section will appear in your project settings.


## Accessing Firewall Configuration
_____________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;


PipeOps provides a simple interface for setting up firewall rules directly within your project settings.

These rules allow you to define which IP addresses or CIDR blocks can access your deployment, and which ports and protocols are permitted for communication.

To access firewall configuration:

- Go to your project dashboard on PipeOps.

- Select the project you want to configure.

\
&nbsp;

![Project dashboard](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/project_dashboard_3a64dfe24e.png)

\
&nbsp;

- Open the Project Settings tab and choose Firewall Rules from the sidebar.

![Project Settings](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Project_Settings_Tab_09f54522db.png)

\
&nbsp;


## Configuring Firewall Rules

_____________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;


### Select Network Traffic Direction

PipeOps lets you configure rules for:

- **Inbound Traffic:** Controls which sources can send requests to your application.

- **Outbound Traffic:** Controls which destinations your application can send traffic to.

![Inbound-Outbound](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Firewall_Inbound_Outbound_aafc4e5020.png)


Click on the Inbound Traffic or Outbound Traffic tab to configure rules for each direction.


### Define Allowed Sources

Specify which IP addresses or CIDR blocks should be allowed.  CIDR blocks allow you to define a range of IP addresses. For example, 10.0.5.0/24 applies your policy to all IP addresses from 10.0.5.0 to 10.0.5.255.

![Allowed Sources](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Firewall_Allowed_Sources_714fe73b4c.png)

You can also:

- Enter multiple IPs separated by commas
- Use predefined keywords like:

   -  any/all – allows traffic from all sources
    
   -  internal – enables secure inter-service communication within your project



### Specify Ports and Protocols

Enter the port number and select the protocol (TCP/UDP).

Expose multiple ports as needed using the **Add More** button.

![Ports and Protocols](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Firewall_Ports_and_Protocols_f0926c73b0.png)

**Save and Apply**

After configuring your rules, click **Save** to enforce them.



## Demo: Applying a Firewall Policy

_____________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;


We’ve just deployed a sample Adonis project on PipeOps. The app is open to everyone by default. In this example, we’ll tighten security by enforcing firewall rules.


When we click the “View Project” button, the application is publicly accessible. Anyone with the link can access it.

![View Project](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/View_Adonis_Project_ce13f9623e.png)

\
&nbsp;



![Adonis Project](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Adonis_Sample_Project_22d3357c90.png)


For this demonstration, we’ll restrict inbound traffic to only allow connections from my IP address over port 443.

![Add Firewall Rule](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Add_Firewall_Rule_f6a64a499c.png)


After applying the firewall rule, only requests from the allowed IP can access the project. All other requests will receive a 403 error.


To confirm the restriction, we’ll test access from a different IP. As expected, the application returns a 403 error.

![403 Error](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Firewall_403_error_1b866fbfdf.png)



### Securing Your Deployment with Confidence

Firewall rules secure your PipeOps deployments by precisely controlling inbound and outbound network traffic. By restricting access to trusted IP addresses and limiting communication to necessary ports, you significantly reduce your application’s exposure to unauthorized access.










How to Enable Firewall Rules on PipeOps 

# What is PipeOps’ Pay-As-You-Go Model and How Does it Benefit You?

__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

In an industry where infrastructure needs evolve quickly, fixed pricing models often lead to overpaying or underutilizing resources. That’s why PipeOps uses a **Pay-As-You-Go (PAYG)** pricing model. This flexible, transparent approach charges you based on what you actually use.


In this article, you’ll learn how the pay-as-you-go model works at PipeOps, who it’s for, and how it can help you control costs while scaling seamlessly.

\
&nbsp;

## Understanding PipeOps’ Pay-As-You-Go Model  


PipeOps’ pay-as-you-go model means you are billed only for the resources you actually use, rather than paying a fixed fee for pre-allocated resources. At the end of each billing cycle, you are charged based on your real usage, ensuring fairness and eliminating unnecessary costs. 

You pay a flat subscription fee to access PipeOps and its features. However, the amount you pay beyond that depends entirely on how much resources you actually use.

\
&nbsp;

### Built-in Usage Coverage

Every PipeOps plan includes a set amount of Nova usage (our managed cloud servers)  covered by your subscription fee.


Here’s how it works:

Growth Plan: $10/month covers $5 in monthly Nova usage

Scale Plan: $150/month covers $50 in monthly Nova usage

You’re only charged for any usage above this coverage.


\
&nbsp;


## Core Principles of the Pay-As-You-Go Model

\
&nbsp;


- **Resource-Based Billing:** You're only billed for the computing resources you actually consume.

- **No Long-Term Commitments:** PipeOps allows you to scale resources up or down as needed.

- **Transparent Pricing:** All costs are clearly visible in your usage dashboard, with no hidden fees or surprise charges at month-end.


\
&nbsp;

## Key Benefits of PipeOps’ Pay-As-You-Go Model
\
&nbsp;


1. **Cost Efficiency and Fairness**

You avoid paying for unused capacity or features. If your usage is low, you keep costs minimal, and if you need more resources, you pay only for your actual consumption. This eliminates waste and aligns cost with value received.


2. **Scalability and Flexibility**

The PAYG model allows you to scale your cloud infrastructure seamlessly, whether you’re a solo developer or a growing enterprise. This flexibility supports dynamic projects and evolving business needs.


3. **Lower Barrier to Entry**

With a modest monthly subscription to access platform features and usage-based pricing, new users and startups can start small without large upfront costs or commitments. This encourages experimentation and innovation without financial risk.

4. **Transparent and Predictable Billing**

PipeOps provides clear usage metrics and pricing details, helping you forecast expenses and avoid surprises. The included usage credits in each plan provide a baseline, and you only pay for overages, making budgeting easier.


PipeOps’ Pay-As-You-Go model allows you to deploy, manage, and scale cloud infrastructure with unmatched flexibility and cost control. Whether you’re a solo developer, a growing startup, or an enterprise, you benefit from transparent billing and the freedom to pay only for what you use.




What is PipeOps’ Pay-As-You-Go Model?

# How to Roll Back Applications in PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

Even with the best CI/CD pipeline, not every deployment goes smoothly. Maybe a dependency breaks, an environment variable is misconfigured, or the new version simply doesn’t behave as expected.

PipeOps helps you recover quickly. With built-in rollback support, you can revert your application to a previously working version in just a few steps.


## When Should You Roll Back? 

You might consider rolling back a deployment when:


- A new version of your app crashes


- Users report issues after a new release


- You need to temporarily revert while investigating a bug


\
&nbsp;

## How Rollbacks Work in PipeOps

PipeOps keeps track of all previous deployments and commit versions. When you initiate a rollback, it redeploys a prior version of your app based on either Git history or deployment history. 

### Initiating a Rollback 


To roll back your application:

1. **Navigate to your project:** Log in to your PipeOps dashboard and open the project.



2. **Open the Actions menu:** Click the “Actions” button in the top-right corner to reveal the dropdown menu.

![Select Rollback](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Select_Rollback_1_3b69d4b560.png)


3. **Select "Rollback":** This opens the rollback modal with two available options:


### Rollback by Git  


Use this if you want to revert based on a specific Git commit.

- Select the **By Git** tab.

![Rollback by Git](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Rollback_by_Git_1_e66e07126e.png)


- Browse your commit history.


- Choose the commit to roll back to.


- Click **Rollback** to initiate deployment.


#### Rollback by Action

Use this if you want to revert to a specific build from your deployment history.

- Select the **By Action** tab.

![Rollback by Action](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Rollback_by_Action_1_428e49da0a.png)


- View previous builds.


- Choose the build version to roll back to.


- Click **Rollback** to begin.


#### Best Practices

-  Roll back quickly when uptime or user experience is at risk.


- Use meaningful Git commit messages—they help when choosing rollback points.


Once a rollback is triggered, PipeOps immediately starts a redeployment. You’ll see a "rollback triggered successfully" notification at the bottom right of your screen. 

![Rollback Success](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Project_Rollback_Trigerred_1_37702dc021.png)



After the process completes, the rollback appears in your deployment history. You can also confirm that the version you rolled back to is now live by clicking the View Project button at the top right of your dashboard.


Rollbacks are a core part of building resilient applications. When things go wrong, PipeOps makes recovery fast, easy, and reliable.




How to Roll Back Applications in PipeOps

# How to Estimate Your Monthly Costs on PipeOps

__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________


Whether you're managing a solo project or scaling infrastructure across teams, understanding what you’ll pay each month is essential for planning and avoiding billing surprises.

In this guide, we’ll walk you through how PipeOps billing works and show you how to estimate your monthly costs with confidence.

\
&nbsp;

## PipeOps' Pricing Structure  


PipeOps uses a transparent, usage-based pricing model made up of:

- **Cloud Resource Usage:** This reflects the cost of the resources you consume. It varies depending on how much you use during your billing cycle.

- **Monthly Subscription Fee:** A fixed amount that gives you access to the platform and its features.


Each subscription plan includes a fixed amount of Nova usage, which is PipeOps’ managed cloud server. This helps offset your resource charges.

\
&nbsp;

| Plan             | Monthly Fee              | Nova Usage Coverage                                      |
| --------           | -------                         | --------                                          |
| Growth         | ₦15,500                    | Covers ₦7,750 in monthly Nova usage            |
| Scale            | ₦232,500                 | Covers ₦77,500 in monthly Nova usage                    |
| Custom         | Varies                      | Custom usage coverage                                      |

  
\
&nbsp;
 
If your usage exceeds the included amount, you’ll only be billed for the extra.

\
&nbsp;

## How to Estimate Your Monthly Cost  


Here’s a simple way to estimate your monthly bill: 

1. Start with Your Plan  

    First, determine your base subscription fee:

    - **Growth:** ₦15,500
    
    - **Scale:** ₦232,500
    
    - **Custom:** Varies


2. Check Your Resource Usage

    Track your current Nova usage directly in your PipeOps dashboard. This helps you see how much resources you’ve consumed so far.


3. Factor in What Your Plan Covers

    Each plan includes a specific amount of Nova usage that PipeOps covers. Subtract this from your total usage.

If your usage is higher than the covered amount, you’ll only pay for the extra. However, if your usage is within your covered amount, you won’t pay anything extra beyond the subscription.

\
&nbsp;


**Example:**

Let’s say User X is on the Growth Plan, which costs ₦15,500/month and includes ₦7,750 in Nova usage. 

This month, User X’s resource usage on PipeOps reached ₦8,000.

Here’s the breakdown:

Subscription fee: ₦15,500

Usage covered in his plan: ₦7,750

Excess usage: ₦8,000 - ₦7,750 = ₦250

For the next billing cycle, User X only pays: ₦15,500 + ₦250 = ₦15,750

\
&nbsp;


## FAQs

### What About “Bring Your Own Cloud” (BYOC) users?

If you're using your own cloud provider (e.g. AWS, GCP, or Azure), PipeOps does not charge you for infrastructure usage. Here’s how it works:

- You only pay the subscription fee.

- Your cloud provider bills you directly for any resources used on their platform.
 
<br>

### Can I switch plans on PipeOps?

Yes, PipeOps allows you to switch between plans. To do this, go to your dashboard and click the profile icon in the top-right corner. From the dropdown menu, select Billing. On the Billing page, click the **Switch Plan** button, choose your new plan, and confirm the change. Your new plan will take effect in the next billing cycle.

<br>

### How do I add or update my payment method?

Go to the Billing section of your dashboard. Under Payment Method, click **Change** and enter your new card or payment details. Your payments will be charged to the updated method.


How to Estimate Your Monthly Costs on PipeOps

## Getting Started Guide: From SignUp to First Deployment
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

If you're new to PipeOps and looking to get your projects up and running quickly, you’re in the right place. This step-by-step guide will walk you through the entire onboarding process—from creating your account to deploying your first project on the platform.  Whether you’re an individual developer or part of a growing team, this tutorial will help you navigate the platform with ease.

This guide will cover three phases:
- Seting up your account
- Choosing your server hosting method
- Project deployment


\
&nbsp;


## Setting Up Your Account​


### Step 1: Visit the homepage 

Open your preferred web browser and navigate to the PipeOps homepage. 
You can use the direct URL: https://pipeops.io.

![landing page](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Landing_Page_9b764ca22e.png)


On the homepage, click the "Sign Up" button at the top right corner of your screen. This will take you to the registration page. 

![landing page](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Signup_f5cb1af420.png)


### Step 2: Sign Up

PipeOps offers four different sign-up options. You can create an account using one of the following:

- GitHub account.
- GitLab account.
- BitBucket account.
- Email address and password.

If you choose GitHub, GitLab, or Bitbucket, ensure that you're already logged into your account. You'll be prompted to authorize PipeOps to connect to your account.

![SigUp Options](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Sign_Up_Credentials_2ada798019.png)


### Step 3: Enter email address and password 

For this guide, we’ll be going with the email sign-up option. Here, you’ll be asked to enter your full name and a valid email address. After that, set a strong password for your account and hit the “proceed” button. 


### Step 4: Verify your email address

After submitting your details, you’ll be redirected to a page requesting your OTP (one-time password). Check your email inbox for the OTP, copy the code, and enter it into the field. Click the “submit” button to proceed. 

![Email Verification](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Verify_OTP_46fc92ff92.png)


### Step 5: Customize your workspace
The next step in your account creation process is to customize your workspace. We want to understand your goal of using PipeOps to provide you with the most relevant features and support. Take a moment to answer the following questions:

**Workspace name**

The first field is to provide a name for your workspace. Your workspace name helps you organize and distinguish your projects within PipeOps.

![Workspace name](https://pub-950943fa1bc54978bed46ef104f9d81a.r2.dev/Documentation%20Images/choose-workspace-name.png)


**Your Role/Job Title**

Choose a role that best describes you from the available options. If your job title is not listed, you can pick “Others” and continue to the next.

![Role](https://pub-950943fa1bc54978bed46ef104f9d81a.r2.dev/Documentation%20Images/role-survey-question.png)


**Project Type**

The next question asks your goal of using the platform. You can select from options, such as exploring PipeOps for your startup, personal project, or open-source project. 

![Goal](https://d23lxlhhocltbo.cloudfront.net/wp-content/uploads/2024/06/28015249/2-2.png)


**Discovering PipeOps**

The final question inquires how you discovered PipeOps. This helps us know how we can reach more people.

![Discover ](https://pub-950943fa1bc54978bed46ef104f9d81a.r2.dev/Documentation%20Images/discovery-survey-question.png)

Click the “Finish” button once you’ve answered this question. Your workspace will be configured accordingly. Now, we can proceed to create a server. 


## Choose your Server Hosting Method 

### Step 1: Select your server hosting option

After the previous step, you’ll be prompted to choose your deployment path. You can decide to deploy your server “On PipeOps” or “On Cloud Provider”. For this guide, we’ll go for the “On Cloud” deployment path.

![Choose path](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_on_pipeops_hosting_475e03e654.png)


### Step 2: Customize your server

After choosing your deployment path, you’ll be directed to:

- Select a cloud provider for your PipeOps Nova server.
- Choose your preferred region: The geographic location for deploying your server. 


![Customize server](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_customize_server_3a0c84e1c7.png)

Click the “Proceed” button to continue.

### Step 3: Select a Plan

Next, you'll see the different subscription plans available on the platform. PipeOps offers three plans: **Growth, Scale,** and **Custom**, with monthly or yearly billing options. 

![Select plan](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_select_plan_b871927ba5.png)


### Step 4: Add payment method

After selecting your preferred plan, a payment modal will appear. Review your subscription and add a payment method. 

You can choose from popular payment options like Stripe and Paystack. After that, click the “Proceed to Subscribe” button. This takes you to the secure checkout page. 

![confirm plan](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_plan_confirm_3182ef5201.png)

### Step 5: Access your Dashboard

Once your payment has been processed, you can now access your dashboard. The next phase is to deploy a project into our newly-created PipeOps server.  

![Access dashboard](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_server_fee7f7b276.png)

<br>


## Project Deployment

### Step 1: Connect your GitHub repository

To deploy your project, you need to first connect your repository provider to PipeOps. For this guide, we’ll be deploying from GitHub, so we’ll select the “Deploy from GitHub” option.

![Connect GitHub](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Connect_Git_e8b8bfc0ac.png)

Authenticate your account to establish a connection between PipeOps and your repository. After successfully linking your Git account, your repository will be available on your dashboard. 

![Linked GitHub](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Linked_Git_Hub_c3cac2e4c2.png)

### Step 2: Select repo source

Click on “Select Git provider account” to reveal a dropdown list from which you can choose “GitHub” or the particular Git provider you linked. Next, click “Select/Add organization” to select your repo organization from the dropdown.

![Select Git Account](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Select_Git_Account_fae45219eb.png)

Now, you can select your repository and the branch you would like to deploy. Click the “Proceed” button to continue. 

![Select Git Branch](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Select_Git_Branch_e14ca71f0c.png)


### Step 3: Configure project

Your Project Summary dashboard will be shown to you. From this page, you can change your project name, select deployment environment, and configure CPU and memory. You can leave everything as default and click Proceed. 

![Project Summary](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Project_Summary_b0166cf4e3.png)

### Step 4: Configure build settings

The next page is for configuring build settings. In build settings > framework, specify your project’s framework. A compatible project build method is set automatically for you. If it’s not, you can choose from the dropdown.

![Project Build](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Project_Build_c29ce0da1f.png)


### Step 5: Deploy project
After reviewing your settings, click the Deploy button. The build process will start and you’ll be able to monitor the logs.

![Project Build Logs](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Project_Build_Logs_57fc0e88e0.png)

Once your project deploys, you’ll see a modal stating that the project has been deployed successfully. Click on “Got it” to go to your project's overview page. 

 ![Successful Project Deployment](https://pub-950943fa1bc54978bed46ef104f9d81a.r2.dev/Documentation%20Images/project-successful-deployment.png)



## Conclusion

And that’s it! You’ve successfully set up your PipeOps account, customized your workspace and server, and deployed your first project. PipeOps is designed to simplify cloud deployment and infrastructure management, and now you’re equipped to explore its full capabilities.







Getting Started with PipeOps: From SignUp to First Deployment

# How to Activate the 14-Day Free Trial on PipeOps  


__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

At PipeOps, we believe in making application deployment effortless for everyone, from solo developers to startups and enterprises. To help you experience everything our platform has to offer, we provide a 14-day free trial that unlocks the features you need to deploy, manage, and scale your applications.



## Step-by-Step: Activating Your 14-Day Free Trial
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

### Step 1:  Sign Up on PipeOps

Visit [pipeops.io](https://console.pipeops.io/auth/signup) to create an account. 


![PipeOps homepage](https://d23lxlhhocltbo.cloudfront.net/wp-content/uploads/2024/06/28014413/Screenshot-2024-06-27-223350.png)

There are different signup methods for your convenience:

- You can sign up using GitHub, Bitbucket, or GitLab.

-  You can also create an account by providing a vaild email address and strong password.
Verify your email by entering the one-time password (OTP) sent to your inbox.

<br>

![PipeOps homepage](https://pub-950943fa1bc54978bed46ef104f9d81a.r2.dev/Documentation%20Images/otp-verification.png)



### Step 2: Customize your Workspace

The next step is to set up your workspace. Here, you'll be prompted to enter a name for your workspace. In PipeOps, a workspace helps you to organize and distinguish projects.


![Workspace name](https://pub-950943fa1bc54978bed46ef104f9d81a.r2.dev/Documentation%20Images/choose-workspace-name.png)


After that, you'll need to provide answers to the following questions:

- What role best describes you

![Role](https://pub-950943fa1bc54978bed46ef104f9d81a.r2.dev/Documentation%20Images/role-survey-question.png)


- The type of projects you plan to deploy

![Goal](https://d23lxlhhocltbo.cloudfront.net/wp-content/uploads/2024/06/28015249/2-2.png)


- How you discovered PipeOps

![Discover ](https://pub-950943fa1bc54978bed46ef104f9d81a.r2.dev/Documentation%20Images/discovery-survey-question.png)


Click on "Finish" to complete.


### Step 3: Create a Server

The next page that appears requires you to choose a hosting method. You have two options when creating a new server: **On PipeOps** and **On Cloud Provider**.


![Choose path](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_on_pipeops_hosting_475e03e654.png)


For this guide, we'll go with the "On PipeOps" hosting method. 


### Step 4: Customize your Server

Choose your preferred provider, select the region you want to use, and click the "Proceed" button.

![Customize server](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_customize_server_3a0c84e1c7.png)


### Step 5: Select a Plan

Next, you'll see the different subscription plans available to you. The Growth Plan will have "**free trial - 14 days**" as shown below. 

![Select plan](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_select_plan_b871927ba5.png)

Click the **subscribe** button to activate your free trial. Keep in mind that this offer is only available to new users. 


### Step 6: Add a Payment Method

A confirmation modal appears after you select your plan. Choose a preferred payment method and click "Proceed to Subscribe."

![confirm plan](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_plan_confirm_3182ef5201.png)


### Access your Dashboard

Once your payment method is confirmed, you'll be taken to your PipeOps dashboard. You can now proceed to deploy applications to your newly-created server. 

![Access dashboard](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_server_fee7f7b276.png)


When you click the **Usage** tab, you'll see you're on the free Growth Plan. You can also view the duration of the free trial on this dashboard. 

![Usage dashboard](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/ft_usage_689ed40a5f.png)


## Conclusion  

Activating your 14-day free trial on PipeOps is seamless. In just a few clicks, you’ll unlock the full power of cloud deployment and automation. Ready to see how easy deployments can be? Sign up today and start building with confidence.

How to Activate the 14-day Free Trial on PipeOps

# How to Deploy Add-ons on PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________


This guide outlines the steps to deploy an add-on in PipeOps. The Add-ons section provides a variety of tools to enhance your projects. From databases to analytics tools, add-ons seamlessly extend your application's functionality.

## Deploying An Add-on

- To deploy an add-on, first log in to your [PipeOps dashboard](https://console.pipeops.io/auth/signup). 

- Click on the "**Addons**" option in the sidebar navigation menu on the left side of your screen. This takes you to the Add-ons marketplace.

![PipeOps Dashboard](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Dashboard_Overview_67745198c7.png)

![PipeOps Dashboard](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Add_ons_Marketplace_7568c3d9ad.png)

- Browse the available add-ons and choose the one you want to deploy.  For this guide, we’ll be deploying Adminer, a web-based database management tool.


- Click on the add-on to view its details. 

![PipeOps Adminer Page](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Adminer_Details_Page_40b5adcc46.png)


## Review Add-on Details

On the add-on's details page, you'll find:

- A detailed description of the add-on's functionality.

- Information about the add-on's creator or provider.

- Any required dependencies.

Once you’ve confirmed it’s the correct add-on, click the "**Deploy App**" button to proceed to the configuration page.

![PipeOps Adminer Page](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Pipe_Ops_Adminer_Deploy_Button_43be3e65cb.png)


## Configure Add-on

![Configure Adminer](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Add_on_Configuration_Page_cc1ee54c69.png)

On the configuration page, you can do the following:

- Select the server where you want to deploy your add-on

- Choose the environment (e.g., beta, development, or production) 

- View the resources required to deploy the add-on and the resources available to you

- Add additional add-ons to deploy alongside the current one

- Review and modify the current configuration settings

## Deploy Add-on

- Once you’ve fully configured the add-on, click the "**Deploy**" button to begin deployment. 

![Configure Adminer](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Add_on_Deployment_In_Progress_fbc5f6beb0.png)


- Upon successful deployment, a success modal will appear. Click the "**Got it**" button to proceed to the [Overview Page](https://docs.pipeops.io/docs/addons/addon-overview) of the add-on you just deployed. 




How to Deploy Add-ons on PipeOps

# Connecting Huawei to PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ 


## Overview

This documentation will guide you through the process of connecting your Huawei account to PipeOps. By following these steps, you’ll be able to create a Huawei server on PipeOps and deploy projects on the server directly from your PipeOps dashboard.


## Steps to follow

To connect your Huawei account to PipeOps, follow these steps:

1. Ensure you have downloaded your Huawei credentials (a CSV file). If not, you can follow the guide [here](/docs/how-to-guides/tutorials/generate-huawei-credentials).

2. On the left menu, click on the "Integrations" tab.

![Cloud Integration Tab](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Cloud_Integration_Tab_51982c1895.png)

3. Click on the Huawei button among the list of cloud providers shown and click the "Connect" button.

![PipeOps Cloud Providers List](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Huawei_Connection_Screen_b775c1cf29.png)

4. An instruction screen appears, outlining the steps required to generate your Huawei credentials.
You can follow the guide [here](https://docs.pipeops.io/docs/how-to-guides/tutorials/generate-huawei-credentials) for a detailed walkthrough.

![Huawei Instruction Screen](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Huawei_Instruction_Screen_f92cb23512.png)


5. On the "Enter Access Credentials" screen, you can provide an optional name to identify your Huawei account. The optional field is useful in scenarios where you want to connect more than one Huawei account on PipeOps. Then provide your "Access Key" and "Secret Key" from the CSV file you downloaded. 


![PipeOps Huawei Credentials Input Screen](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Huawei_Credentials_Upload_11a2f32896.png)

6. Click on the submit button at the bottom right. If the Huawei credentials are valid, your Huawei account will be successfully connected.


Now that you've connected your Huawei account to PipeOps, you can create a server on your connected Huawei account using this [guide](https://docs.pipeops.io/docs/servers/server-provisioning).



How to Connect Huawei to PipeOps

# Connecting GCP to PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ 


## Overview

This documentation will guide you through the process of connecting your GCP account to PipeOps. By following these steps, you’ll be able to create a GCP server on PipeOps and deploy projects on the server directly from your PipeOps dashboard.


## Steps to follow

To connect your GCP account to PipeOps, follow these steps:

1. Ensure you have downloaded your GCP JSON credentials. If not, you can follow the guide [here](https://docs.pipeops.io/docs/how-to-guides/tutorials/generate-gcp-json-credentials).

2. On the left menu, click on the "Integrations" tab.

![Cloud Integration Tab](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Cloud_Integration_Tab_51982c1895.png)


3. Select "Google Cloud Platform" from the list of cloud providers shown and click the "Connect" button.

![PipeOps Cloud Providers List](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/GCP_Connection_Screen_610ba6b373.png)

4. An instruction screen appears, outlining the steps required to generate your GCP credentials.
You can follow this guide [here](https://docs.pipeops.io/docs/how-to-guides/tutorials/generate-gcp-json-credentials) for a detailed walkthrough.

![GCP Instruction Screen](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/GCP_Instruction_Screen_a531f5f73d.png)

5. On the "Upload Credentials JSON" screen, you can provide an optional name to identify your uploaded GCP JSON credentials. The optional field is useful in scenarios where you want to connect more than one GCP account on PipeOps.

![GCP JSON Credentials Upload Screen](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/GCP_JSON_Credentials_Upload_2ee21ee514.png)

6. Click on the submit button at the bottom right. If the JSON credentials are valid, your GCP account will be successfully connected.



Now that you've connected your GCP account to PipeOps, you can create a server on your connected GCP account using this [guide](https://docs.pipeops.io/docs/servers/server-provisioning).



How to Connect GCP to PipeOps

# Connecting Digital Ocean to PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ 

## Overview

This documentation will guide you through the process of connecting your Digital Ocean account to PipeOps. By following these steps, you’ll be able to create a Digital Ocean server on PipeOps and deploy projects on the server directly from your PipeOps dashboard.

## Steps to follow

To connect your Digital Ocean account to PipeOps, follow these steps:

1. In the PipeOps Dashboard, click on the "Integrations" tab from the left menu.

![Cloud Integration Tab](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Cloud_Integration_Tab_51982c1895.png)

2. Select "Digital Ocean" from the list of cloud providers and click "Connect" to proceed. 

![DO Connection Screen](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/DO_Connection_Screen_bf950aba66.png)

3. On the **Authorize DigitalOcean** screen, click the "Authorize my Digital Ocean" button. This will open a new tab to the right.

![DO Authorization Screen](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/DO_Authorization_Screen_87b3dc76a8.png)

4. You will be redirected to DigitalOcean’s authorization page, as shown below. Click the "**Authorize Authorization**" button to grant PipeOps the necessary permissions.

![Authorize PipeOps on DO](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Authorize_Pipe_Ops_on_DO_Tab_d06ee3371f.png)

5. After authorization, you will be redirected back to PipeOps. If successful, you'll see DigitalOcean listed as a connected provider.

![Successful DO Integration](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Successful_DO_Integration_137892265a.png)

Now that you've connected your Digital Ocean account to PipeOps, you can create a server on your connected account using this [guide](https://docs.pipeops.io/docs/servers/server-provisioning).

How to Connect Digital Ocean to PipeOps

# Connecting Azure to PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ 



## Overview

This documentation will guide you through the process of connecting your Azure account to PipeOps. By following these steps, you’ll be able to create an Azure server on PipeOps and deploy projects on the server directly from your PipeOps dashboard.


## Steps to follow

To connect your Azure account to PipeOps, follow these steps:

1. Ensure you have your Azure credentials. If not, you can follow the guide [here](https://docs.pipeops.io/docs/how-to-guides/tutorials/generate-azure-credentials).

2. On the left menu, click on the "Integrations" tab.


![Cloud Integration Tab](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Cloud_Integration_Tab_51982c1895.png)


3. Select "Azure" from the list of cloud providers and click the "Connect" button.

![Azure Connection Screen](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Azure_Connection_Screen_8ee52cad10.png)

4. An instruction screen appears, outlining the steps required to create your Azure credentials.
You can follow this guide [here](https://docs.pipeops.io/docs/how-to-guides/tutorials/generate-azure-credentials) for a detailed walkthrough.

![Azure Instruction Screen](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Azure_Instruction_Tab_d16cefcb3a.png)

5. On the "Enter Access Credentials" screen, you can provide an optional name to identify your Azure account. The optional field is useful in scenarios where you want to connect more than one Azure account on PipeOps.

![Azure Instruction Screen Filled](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Azure_Connection_Screen_Filled_b59ab96305.png)

Fill in the required fields with your credentials:

- Resource Group Name
- Tenant ID
- Client ID
- Client Secret
- Subscription ID

6. Click the submit button. If the credentials are correct, PipeOps will successfully integrate with Azure.

![Successful Azure Connection](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Successful_Azure_Integration_1221c9e8ba.png)

Now that you've connected your Azure account to PipeOps, you can create a server on your connected Azure account using this [guide](https://docs.pipeops.io/docs/servers/server-provisioning).

How to Connect Azure to PipeOps

# Connecting AWS to PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ 


## Overview

This documentation will guide you through the process of connecting your AWS account to PipeOps. By following these steps, you’ll be able to create an AWS server on PipeOps and deploy projects on the server directly from your PipeOps dashboard.

## Steps to follow

To connect your AWS account to PipeOps, follow these steps:

1. On the left menu, click on the "Integrations" tab.

![Cloud Integration Tab](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Cloud_Integration_Tab_51982c1895.png)

2. Select AWS from the list of cloud providers shown and click the "Connect" button.

![PipeOps Cloud Providers List](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Cloud_Provider_List_ff348bfbe8.png)

3. On the "Connect AWS" screen, you can provide an optional name to identify your AWS account. The optional field is useful in scenarios where you want to connect more than one AWS account on PipeOps.

![AWS Connection screen](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/AWS_Connection_Screen_175273010d.png)

4. Fill in your AWS Account ID found at the top-right corner of your AWS account and an optional name.

![AWS Connection screen filled](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/AWS_Connection_Screen_Filled_6dbfafcb65.png)

5. After filling out the form, click on the "Add" button. A spinner loads, enabling the "Authorize IAM" button.

6. Click on the "Authorize IAM" button. It should open a "Create Stacks" page in a new tab in your AWS account, which will prompt you to acknowledge "that AWS CloudFormation might create IAM resources with customised names" on the bottom of the page. 

Click on the "Create stack" button at the bottom right of the page.

![AWS Create Cloud Formation Stacks Page](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/AWS_Cloud_Formation_Page_65d73f635d.png)

7. After clicking the "Create stack" button. You will have a page similar to this.

![ AWS Create Cloud Formation Stack In Progess Page](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/AWS_Cloud_Formation_Stack_in_Progress_e96537f489.png)

8. You can switch back to your PipeOps tab to the left and wait for a few seconds and your AWS account will automatically get connected.

![Successful AWS Integration Page](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Successful_AWS_Integration_f69a665941.png)

Now that you've connected your AWS account to PipeOps, you can create a server on your connected AWS account using this [guide](https://docs.pipeops.io/docs/servers/server-provisioning).



Guides