

Your PipeOps account dashboard gives you full control over your personal profile, team settings, billing preferences, and usage overview. Whether you're updating your name, inviting teammates, switching plans, or removing a payment method, this guide walks you through all available actions under your Account Profile.

To reveal the account settings dropdown, click the power icon at the extreme right of your dashbaord:

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/85/Select_profile_6157151293.png)


## Profile

This section allows you to update your personal details, such as full name and change your password. 

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/85/Account_details_edb0d1ae79.png)



You can remove and add payment methods from this section. The Profile segment also allows you to connect and disconnect repository providers. 

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/85/Account_git_and_repo_61d06055b4.png)


## Teams
The Teams section lets you manage collaboration settings and project access.

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/85/Account_teams_0e281344de.png)

From here, you can:
- Create and delete teams
- View team members and track their actions in the workspace
- Invite or remove teammates
- Assign roles like Admin, Member, Guest

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/85/Account_team_details_9d3dece51c.png)

Learn more about how to [collaborate with team members](https://pipeops.io/resources/guides/30/how-to-collaborate-on-pipeops-projects).


## Usage

The Usage section gives you insight into how you are consuming PipeOps resources. You can understand how different projects or add-ons contribute to your monthly charges from here. It also provides a detailed overview of your subscription plan, resource usage, and available credits. You can manage team seats, deployments, and credit top-ups from this section.

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/85/Account_usage_9330aa948c.png)

## Billing
The Billing tab lets you manage everything related to your subscription and payment methods.
Here, you can:


- View your current plan 
- Switch between monthly and yearly billing
- Add or remove payment cards
- View billing history and download invoices


![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/85/Screenshot_2025_07_31_223316_691080dd78.png)


## How to Remove a Payment Card
You may want to remove an old or expired card from your account.
To remove a card:
- Scroll to the Payment Method tab below Current Plan.
- Select Remove Card.
- Confirm the removal in the prompt that appears.

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/85/Screenshot_2025_07_31_225208_a97f739b5d.png)

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/85/Screenshot_2025_07_31_223404_4f4088aa4b.png)


Note: You must cancel your subscription before removing your primary payment method. If you have multiple cards on file, you can remove any non-primary card without canceling your subscription. To update payment options, click the Update button.


## Final Thoughts
Managing your PipeOps account is simple, and knowing where to look saves you time. From inviting teammates and checking your usage, to removing a payment method, everything is available from your Account Settings panel.

For questions about billing, switching plans, or resolving card errors, you can always contact support.





How to Manage Your PipeOps Account


Custom domains make your application more professional and easier for users to remember. With PipeOps, connecting your domain is fast and secure.


This guide walks you through adding a domain and updating your DNS settings so your app is accessible via your own domain name.





**Prerequisites**

Before you begin, make sure:

- You’ve deployed a project on PipeOps. 


- You own the domain you want to connect (e.g., via Namecheap, GoDaddy, etc.).

- You can access your DNS provider’s dashboard to edit DNS records



For this guide, we’ve deployed a project that’s currently accessible via a pipeops.app endpoint.


![react app demo](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/83/vite_project_5c5637e494.png)



&nbsp;


## Step 1: Go to Your Project Settings


- Log in to your PipeOps Dashboard


- Select the project you want to connect the domain to


- Navigate to Settings and select Domains from the left menu


- Enter the full domain name (e.g., mydomain.com) in the text field that appears


![custom domain](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/70/83/add_domain_name_026fa189e9.png)



- Click “Save”


PipeOps will generate the DNS records you need to add to your domain registrar.


![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/83/DNS_record_8fe63d441e.png)



&nbsp;
## Step 2: Update Your DNS Records

In your domain registrar’s DNS settings, add the CNAME record exactly as shown in the PipeOps dashboard.

Tip: If you're pointing a root domain (like mydomain.com), set the Host field to @.


![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/83/Submit_DNS_record_970a25604c.png)

&nbsp;


## Step 3: Wait for DNS Validation

After saving your DNS records, the system will automatically detect the new records and validate the domain.

It can take a few minutes to a few hours for your DNS records to propagate.




&nbsp;

### Testing Your Setup

Visit your custom domain in a browser. If the DNS is set up correctly, you should see your PipeOps-deployed project load securely using your domain.

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/83/custom_project_ebf678794f.png)











How to Connect a Custom Domain to Your PipeOps Project

Deploying on PipeOps is seamless. The platform detects your app’s language, applies the appropriate buildpack, and launches your application using a default command. But sometimes, your app builds successfully, yet fails to deploy.

When deploying your app, one challenge you may face is not specifying how it should start. In most cases, this issue can be resolved by adding a simple Procfile to the root of your project. This guide explains what a Procfile is and how it helps fix deployment issues. 


&nbsp;


## Using a Procfile to Define the Start Command

---

PipeOps uses buildpacks to automate language detection, dependencies, and start commands. However, buildpacks depend on standard project layouts. If your app deviates from that structure, like missing a start script, the build may succeed while the deployment phase fails.


A Procfile gives you full control over how your application is started. It overrides the default start command provided by the buildpack and lets you specify exactly what should run when your app boots.

This method is not limited to any single language. It works with Node.js, Go, Python, Java, Rust, and more.


&nbsp;

### What Is a Procfile?

A Procfile is a plain text file, named exactly Procfile (no file extension), placed in the root of your project.

Each line defines a process type and the command to run:

```
<process type>: <command>
```

process type: this is an alphanumeric name for your command, such as web.

command: this indicates the command the process type should execute on startup.




&nbsp;

## How to Create a Procfile

---

1. In the root directory of your project, create a file called:

``` Procfile ```

Note that:

- It must be named exactly Procfile (case-sensitive, no .txt or .conf)
- It must be in the root, as it won't be detected from subfolders


&nbsp;

2. Inside the file, write the process type and start command:

 ``` 
web: <your-app-start-command>

```

Example:  

For a Java Spring Boot application with an executable JAR file named app.jar in the target/ directory, the Procfile might look like:


```
web: java -jar target/app.jar
```

&nbsp;

## How this Works with PipeOps Buildpacks

---

When you deploy on PipeOps using the Recommended Build Method, here’s what happens:


- PipeOps detects your app language via a buildpack.


- It uses the buildpack’s default start command.


- If a Procfile is present, your custom command takes precedence.


- Your app runs as defined, giving you full control.


This makes the Procfile a powerful override mechanism. 


&nbsp;
## Summary
A Procfile is not generally required to deploy applications as the platform automatically detects the app’s language and creates a default web process type to start the application server. However, including an explicit Procfile provides greater control and flexibility over how your app runs.








 Using a Procfile to Define Custom Start Commands



If your account has been restricted and you're unable to renew or cancel your subscription, it might be due to unpaid Nova usage. This guide walks you through how to clear those charges using your available credit (wallet), a payment provider, or both.

&nbsp;

## Why Am I Seeing a Restriction Notice?

When you log in to your PipeOps dashboard, you may see the following alert, “Your account has been restricted due to unpaid usage."

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/81/restriction_banner_13f5570c18.png)


Also, when trying to subscribe or cancel, you may see a pop-up modal that says you’ve incurred some Nova resource usage charges that need to be settled before you can renew your subscription. 

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/81/renew_subscription_payment_required_modal_89af452d4f.png)


![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/81/cancel_susbscription_modal_c17258ddb3.png)


This means you have an unpaid Nova invoice and need to clear it before continuing.
Depending on your situation, you’ll need to pay before you can:


- Subscribe to a new plan or upgrade
- Unsubscribe from your current plan


&nbsp;


## How to Pay for Nova Usage

You can pay directly from your PipeOps Wallet, with your saved payment method (Stripe or Paystack), or a combination of both. You can clear your outstanding charges using any of the following methods:


**A. From the Dashboard Banner:**

- At the top of your dashboard after login, there’s a  banner that tells you about unpaid usage.
The banner includes a "Pay Now" button. Click this button to proceed directly to the payment (checkout) page.

![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/81/restriction_banner_13f5570c18.png)

**B. While Renewing your Subscription:**

- At the billing section, when trying to renew or cancel, a modal appears indicating the exact amount owed.




![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/81/renew_subscription_220c21fb6c.png)


![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/81/renew_subscription_payment_required_modal_89af452d4f.png)



- Click the "Pay Now" button to redirect to the payment checkout page for your outstanding bill.


&nbsp;

### Checkout Tab

Once the checkout tab opens, you have different payment options.

**Pay from Your Wallet:**


If you have enough funds in your wallet balance, you will see the option to pay directly from your in-app credits.

- Enable the “Apply Credit” toggle to use your wallet balance.

- Complete the payment with your wallet if it covers the full outstanding amount


![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/69/81/pay_now_checkout_4fa3a73b8f.png)

**Pay with Payment Provider:**

You can use either Paystack or Stripe as payment methods:

- Paystack: Ideal for local payments.
- Stripe: Ideal for international customers.
    


&nbsp;

**Split Payment:**

- If your wallet balance does not cover the entire amount, you can pay a portion from your wallet and the remainder via a payment provider.

- The system will prompt you to pay the outstanding remainder using Paystack or Stripe.


&nbsp;

### Complete the Payment
Once the payment is successful, your NOVA usage charges will be marked as settled, and restrictions will be lifted.


&nbsp;

### Still Restricted After Payment?

If you’ve completed payment but still see the restriction banner:

- Refresh your browser window

- Check if the restriction clears automatically

If not, contact support from your dashboard or email us at support@pipeops.io










How to Pay for Outstanding Nova Usage

##  How to Toubleshoot Deployment Failures on PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;



You start deploying your application and something goes wrong. What do you do?
Deploying applications can usually go unexpectedly. This guide provides troubleshooting tips that can help you resolve common issues.


\
&nbsp;


## Check Deployment Logs


If your project fails to deploy or start, you can check what’s the cause in your build logs and app logs. Often, the errors shown there are descriptive enough to point you in the right direction.


You can access build logs during the deployment process to debug issues like missing dependencies, failing steps, or syntax errors that prevent a successful build.  App logs are also available for runtime logs from the application.



**Example:** In the logs below, we see that the deployment failed due to a MongoDB connection issue. This tells us where to look.

![Logs error](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/App_Logs_Error_33d314dd8e.png)

After checking our environment variables, we realized that the database name in the MONGO_URI connection string was incorrect.

Once we updated the value and redeployed the project, the deployment completed successfully.

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

Bottom line: Logs offer insight into the build and deployment process. If anything goes wrong, they are often your best bet in finding out the root cause of the problem.



\
&nbsp;

## Use the Events Timeline

We highly recommend checking the Events tab. It provides a chronological list of actions related to your deployment, like "Pulled image,"  "Container started," "Startup probe failed," and so on. This is especially useful for understanding when and where something went wrong.


To view events associated with your deployment:

- Navigate to your project.
- Click the "Events" tab as shown below.

![Check Events](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Events_Tab_63de9e440d.png)


\
&nbsp;


## Verify Environment variables

Your deployment can fail if the port it exposes doesn’t match the one you set in your PipeOps environment variables. For example, your application can build successfully yet fail to deploy.

Here’s how to confirm your environment variables are correctly configured:

- Go to your project settings
- Access the environment variables tab
- Verify that the PORT and other variables are correctly set

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

\
&nbsp;


## Auto-Deployment & Repository Visibility Issues

If your project doesn’t pick up new changes made to your GitHub repository, you can fix that by installing the PipeOps Git App. This solution also works for situations where you don’t see your private repositories when trying to deploy.

To install the PipeOps Git app:

- Follow the process for deploying a web project
- Select your GitHub account
- Click the “Install PipeOps Git” button

![Install PipeOps Git](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Install_Pipe_Ops_Git_9e293884ea.png)


Once installed:

- Auto-deployments will trigger correctly on new commits.
- Private repositories will become visible when selecting repos.


\
&nbsp;


## Validate Configuration Files

Incorrect or incomplete configuration files are a frequent source of deployment errors. 
Common culprits include Dockerfile, package.json (for Node.js apps), next.config.js (for Next.js), .env.example, etc.

What to do:

- Ensure your files are valid and present in your repository.

- Confirm that these files have the right syntax and content.

- Double-check that start scripts exist and run as expected locally.




\
&nbsp;

## Additional Troubleshooting Tips

- **Avoid unnecessary lifecycle commands:** Adding a lifecycle command without verifying that it works can break your deployment. Only add what you need, and test locally first.


- **Check for missing dependencies**: If a required package isn’t listed in your project’s dependency file, your deployment may break. Double-check that all needed packages are included in package.json, requirements.txt, etc.






\
&nbsp;



Deployment issues can be frustrating, but most have clear, repeatable fixes. With this guide and the tools available on PipeOps, including logs and events, you can identify problems faster and ship confidently.

If you’ve tried these solutions and still need help, don’t hesitate to reach out.






Troubleshoot Deployment Failures on PipeOps


&nbsp;


PipeOps provides different types of services for your application, including databases. 
This guide walks you through how to deploy a database and connect it to your application. 

For the purpose of this guide, we’ll be deploying MongoDB.

## Deploy a Database

Deploying a database on PipeOps is designed to be straightforward, even for users with minimal experience. Log in 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 your desired database from the addon marketplace. You can use the search bar if the database is not immediately visible. 

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

On the add-on details page, click on “Deploy App.”

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

On the configuration page, select your desired server and environment.

PipeOps allows communication only over a private network at the moment. To ensure successful connection, both the application and the database must be deployed on the same server. Internal networking only works across services running on the same server on PipeOps.

Click on “Deploy” to start the deployment process. In a few seconds, your database instance will be successfully deployed.

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


### Retrieve Database Connection Details

Click on your deployed database. On the overview tab, you’ll find the connection details for your database. For instance, for our MongoDB instance, we’ll find the following parameters:


      userName
       password
       databaseName
       port
       Host


![MongoDB parameters](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Mongo_DB_Connection_Parameters_191015d83e.png)


You can click on the dropdown under connection details to find your connection string.

These parameters are also available in the environment variables section of your deployed database. Click on the settings tab and select environment variables. 

![MongoDB env](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Mongo_DB_Env_9c6ba211e6.png)


## Connect Your Application


In your app’s environment variables, set the database connection string copied earlier.

You can connect to your database from another service in your project by referencing the environment variables made available in your database settings tab. 

Many libraries will automatically look for the DATABASE_URL variable and use it to connect, but you can use these variables in whatever way works for you.



For this guide, we will have an environment variable setup using MongoDB URI:


        MONGO_URI=mongodb://user:password@host:port/databaseName



Let’s deploy our application. 


Click the "+ New" button at the top right of your dashboard to deploy your application. 

Next, select your repository and the branch you'll deploy from. Click "Proceed" to continue.

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




Select your framework on the Build Settings page. Under Environment Variables, we’ll add:

    Key: MONGO_URI 

    Value: mongodb://user:password@host:port/databaseName


Replace “user” “password” “host” “port” and “databaseName” with the actual values from your database connection parameters. 


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


Also, ensure your app’s database client will be using the connection string. 

For example, in our nodeJS app, we have:


![Use Variable ](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Mongo_Code_b8ba445e89.png)


Click "Deploy Project" to start the deployment process.

When we check our app logs, we’ll see a successful connection as shown below:



![DB connected ](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/20/69/Successful_DB_Connection_cd3baf2962.png)


You’ve now seen how to set up a working connection between your application and a database on PipeOps. This approach works similarly for other databases like PostgreSQL or MySQL too.



How to Communicate with Databases Deployed on PipeOps

# 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

## 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.

Want to link a custom domain to your application? Check this detailed guide on how to
[connect a custom domain to your pipeops project](https://pipeops.io/resources/guides/35/how-to-connect-a-custom-domain-to-your-pipeops-project).







Getting Started with PipeOps: From SignUp to First Deployment

# 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

# 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.

Guides