Get the Best of Both Worlds

with Codeship's Enterprise Support

Sign up for freeStart a conversation

Use your private, self hosted SCM and run CI/CD builds in the cloud with Codeship.

Hybrid Workflow

Our hybrid approach lets you maximize value on both ends. You’ll be running your builds in the cloud, on our build machines, while hosting your code on your private SCM instance.

Improved Security

Improved security design, from dedicated build machines to never storing your code, to make running builds in our cloud safe even if you have security or organization needs for on-prem source control.

Scalability

As your projects and team grow, your commits increase, your tests require larger build machines or more parallel pipelines. We offer plans that can scale with your needs. Codeship can handle any size team or project.

Current Integrations

Status: Live

 

ICN-Focus.png

 

Start running builds with GitHub Enterprise on Codeship. 

Learn more

ICN-Focus.png

 

Start running builds with GitLab CE & EE on Codeship. 

Learn more

ICN-Focus.png

 

Start running builds with Bitbucket Server on Codeship.

Learn more

 

New Features

 

ICN-Focus.png

Two Factor Authentication

Keep your code even more secure with two-factor authentication sign in, a feature important to your security.
 
Learn more
ICN-Focus.png

IP Whitelisting

With our IP Whitelisting feature, it’s now much easier to grant Codeship infrastructure access to internal systems in a limited way. 
 
Learn more

These companies already love Codeship

travelperk
Wholefoods.png
Harvard.png
CNN.png
Redbull.png
autodesk-1.png
Common Questions

Common Questions

Why the on-premise/cloud solution?

We opted to build this hybrid solution to enable organizations to support internal security policies without taking on the overhead of managing their own CI/CD Servers.

This solution lets you host your code on-premise on your private source code management instance while letting you run your builds securely in the cloud on Codeship’s secure, dedicated build machines

Which IPs do I need to whitelist?

Right now, we require that the necessary ports be open to the public, or that you be able to whitelist the entire us-east-1 AWS region for those ports.

Soon, we will begin beta on our feature to limit the range of IPs your build machines run in so that you can whitelist only a small handful of IPs for the required ports. Get in touch if you’d like to sign up for this beta, or read about the setup requirements here

 

Can I run it within my VPC?

Codeship has embraced the cloud, as well as hybrid workflows for maximum ROI. We do not install Codeship on your VPC, instead running on our highly secure build machines.

This means that you can keep your code secure in GitHub Enterprise while keeping costs and overhead low by leveraging a cloud CI/CD environment.

Which ports do I need to open?

You will need to open ports 22 and 433 to be publicly available. These ports let us clone your repositories, as well as report back build status.

You can learn more about our setup in our documentation 

How do you ensure security?

We take security incredibly seriously. From our system design to admin controls, we’ve built Codeship with the understanding that keeping your code and your environments secure is critical.

You can read our documentation article on our security policies or you can let us know if you have a specific security question or would like to request a copy of our in-depth security audit.

How much does this cost?

GitHub Enterprise support on Codeship doesn’t cost anything extra! The same pricing for our Github.com applies to GitHub Enterprise. You can view our pricing page or get in touch if you’d like ask a question. 

Upgrading your subscription in between a subscription period is prorated. You are able to cancel your subscription any time.

Have more questions about our Enterprise Support?
Start a conversation