Local CI
A Continuous Integration tool for Bitbucket repositories with focus on Security, Cloud costs reduction, Easy Pipeline Debugging, No build queue.
LocalCI helps you to reduce Cloud costs filtering bad
commits before a Cloud continuous integration pipeline is triggered.
Benefits ❤️
An overview of the main benefits using LocalCI as a continuous integration tool
Code repository security
Existing CI commercial products run your private code on external public cloud infrastructures or they give you the option to have expensive CI solution on-premise.
LocalCI allows you to keep your code into your IT network organization. All the builds run into an isolated docker network, hosted in the developer machine.
Easy Pipeline Debugging
Debugging CI pipeline on hosted external machine is one of the main limitations of existing CI products.
LocalCI allows developers to keep control of your CI pipeline. They can easily debug the CI pipeline in Debug mode.
No build queue
One of the main limitations of using existing CI products is the multi-users cloud build queue.
LocalCI improves the performance of your CI pipeline, you can run CI pipeline Immediately on your own machine with the same reliability you can have on Cloud
Cloud costs reduction
Most of the CI companies charge you using "credit-based usage plans", "cost per number of concurrent builds", "costs based on vCPUs and memory used per hour".
LocalCI helps you to reduce Cloud costs by filtering bad
commits before a Cloud CI pipeline is triggered.
Getting started 🚀
Get set up and start working with LocalCI in minutes.
Customers feedbacks 📨
— Cloud costs reduction is always a hot topic for big organizations. An hybrid approach with LocalCI could be a solution. We still have our legacy cloud ci in place but Thanks to LocalCI (running on dev machine) we have reduced >60% of our CI Cloud costs.
FEATURES 💡
We have built a list of essential features in order to simplify the developer CI experience.
CI Debug Mode
You can run your CI process in Debug mode. You will be able to fix/edit your YAML file. You can even expose a port for debugging your code.
CI Pipeline Flow
LocalCI desktop app runs automatically your builds. Every build will be triggered by specific Git Hooks script. At the end of each build the CI pipeline status will be displayed on your Bitbucket repository.
Desktop Notifications
How long should a CI build take? You can easily monitoring the CI process using our LocalCI desktop notifications.
User Identity
User identity is protected by Auth0 provider (https://auth0.com/). Auth0 allows us to have a seamless integration with your Enterprise IT infrastructure. We can connect your employees using: SAML. Active Directory/LDAP, Microsoft Azure ID, ADFS, Open ID Connect, Google Workspace, Ping federate. (Contact us for more informations)
Docker Network
LocalCI desktop app runs your build pipeline into an isolated Docker network. Users can access the Docker network only in Debug mode
Bitbucket Admin Control
Only Bitbucket Admin users can edit LocalCI settings. Admin users can decide when the local ci pipeline will be triggered.
CI Monitor
Your CI pipeline results will be displayed in our LocalCI web site. Your team will be able to see your CI results only if they have access to your repository.
CI Pipeline Configuration
You can configure the ci pipeline using our custom yaml file.
Simple, transparent pricing
You can start using LocalCI with a simple Free plan. No card details is required. If your git repository has more than 3 users you need to upgrade your plan.
- Desktop App
- Access to LocalCI web
- Bitbucket Admin control
- Bitbucket CI status update
- > 3 Bitbucket users per repository
Free
Premium
- Desktop App
- Access to LocalCI web
- Bitbucket Admin control
- Bitbucket CI status update
- > 3 Bitbucket users per repository
€ 6.90 per user/month
€ 6.90 per unique user during 1 month. If your Bitbucket repository has 10 users your final payment will be € 60.90 per month. If you add and remove 1 user in the same month, the user will be counted into your monthly payment.