--- description: Get detailed information about LayerCI and how it can help you meet your business needs. Learn more about LayerCI price, benefits, and disadvantages for businesses in Singapore. image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: LayerCI Pricing, Cost & Reviews - Capterra Singapore 2026 --- Breadcrumb: [Home](/) > [DevOps Tools](/directory/31120/devops/software) > [LayerCI](/software/202546/layerci) # LayerCI Canonical: https://www.capterra.com.sg/software/202546/layerci Page: 1 / 2\ Next: [Next page](https://www.capterra.com.sg/software/202546/layerci?page=2) > Developers ship changes faster by using LayerCI provisioned VMs for E2E tests and full-stack website previews. > > Verdict: Rated **4.8/5** by 13 users. Top-rated for **Likelihood to recommend**. ----- ## Overview ### Who Uses LayerCI? Companies with software developers ## Quick Stats & Ratings | Metric | Rating | Detail | | **Overall** | **4.8/5** | 13 Reviews | | Ease of Use | 4.8/5 | Based on overall reviews | | Customer Support | 5.0/5 | Based on overall reviews | | Value for Money | 5.0/5 | Based on overall reviews | | Features | 4.7/5 | Based on overall reviews | | Recommendation percentage | 90% | (9/10 Likelihood to recommend) | ## About the vendor - **Company**: LayerCI - **Founded**: 2018 ## Commercial Context - **Starting Price**: CA$35.00 - **Pricing model**: Flat Rate (Free version available) (Free Trial) - **Target Audience**: Self Employed, 2–10, 11–50, 51–200, 201–500 - **Deployment & Platforms**: Cloud, SaaS, Web-based - **Available Countries**: Canada ## Features - Dashboard - Release Management ## Support Options - Chat ## Category - [DevOps Tools](https://www.capterra.com.sg/directory/31120/devops/software) ## Alternatives 1. [Cloudsmith](https://www.capterra.com.sg/software/177474/cloudsmith-package) — 4.5/5 (22 reviews) 2. [SlickStack](https://www.capterra.com.sg/software/211436/slickstack) — 5.0/5 (16 reviews) 3. [Pulumi](https://www.capterra.com.sg/software/1020825/pulumi) — 4.7/5 (3 reviews) 4. [Release Lifecycle Management](https://www.capterra.com.sg/software/170551/release-lifecycle-management) — 4.8/5 (5 reviews) 5. [Chocolatey](https://www.capterra.com.sg/software/210185/chocolatey) — 4.8/5 (6 reviews) ## Reviews ### "The new target for modern CI" — 5.0/5 > **Gabriel** | *16 February 2021* | Information Services | Recommendation rating: 9.0/10 > > **Pros**: - Speed. Layer caching allows most runs to complete unreasonably fast - 10x faster than our legacy CI. This is because of how Layer allows us to architect our CI to setup the environment once and reuse across many similar micro-services. - Simple. Since Layerfiles are similar to Dockerfiles, it is fairly intuitive to jump in and create your CI flows. > > **Cons**: Since LayerCI is still a young company, there are some commands and features that are not yet in place. There hasn't been anything we couldn't work around and the team is working fast to add additional native features to solve for these edge cases. > > Overall the team is incredibly responsive and adaptive to our needs and we've been continuously increasing the complexity of our LayerCI implementation as we build our core stack. ----- ### "Layer made everything easier" — 5.0/5 > **Matthew** | *9 July 2020* | Commercial Real Estate | Recommendation rating: 9.0/10 > > **Pros**: We had to deploy to our custom staging environment every time we wanted to test before - this cost us an incredible amount of time, especially since we work on many different features concurrently. We didn't have the time or need to set up a full solution, and Layer was a perfect medium between convenience, cost, and flexibility for us. > > **Cons**: There's no free trial, and it's still quite difficult to understand how to set your build up coming from a zero-experience background. I was hesitant until I saw how dedicated the customer support was, and then it was a no-brainer. > > Atmos used to have several bugs leak into production because we couldn't properly or efficiently deploy our code to a staging environment. Changes required a manual deploy, slowing down our development and QA speed. Layer made it simple: commit your changes, check if it works in Layer, then keep going. ----- ### "LayerCI - Fast and easy CI tool" — 4.0/5 > **Umar** | *30 April 2020* | Hospital & Health Care | Recommendation rating: 8.0/10 > > **Pros**: LayerCI was easy and fast to integrate and setup as part of my CI pipeline. The command structure was also easy to understand and very easily integrated with the scripts I was previously using to manually deploy my code. In addition, \[SENSITIVE CONTENT HIDDEN\] has been very responsive to answering any questions I might have about the software and recommended practices. > > **Cons**: There is still some polishing needed to smooth out the rough edges. e.g. sometimes the caching was too effective. > > My overall experience with LayerCI so far has been great. I especially loved the customer service and fast response times. ----- ### "Fast and flexible CI" — 5.0/5 > **Misha** | *14 May 2020* | Education Management | Recommendation rating: 10.0/10 > > **Pros**: LayerCI's speed makes testing and deployment easy and quick and saves me time. Other CI tools I have used often take minutes to set up an environment that takes seconds with LayerCI. This drastically speeds up my workflow and means I can accomplish more tasks in a day. > > **Cons**: The Layerfile syntax is based on the Dockerfile syntax with a few subtle differences. I would like to see some more documentation with regards to the differences between the two so that I can write better Layerfiles in the future. ----- ### "Great product for quick validation of changes to your software" — 5.0/5 > **Xin** | *16 February 2021* | Internet | Recommendation rating: 10.0/10 > > **Pros**: Once you have it set up and get an ephemeral environment you can do a lot of things with it. We use LayerCI at Welcome to do internal testing and also just product feature previews for internal users. We use it for our weekly demos as well sometimes. It can also be used to run tests to validate a feature. We have seen developers use the personal ephemeral environments to test multiple changes at a time without having to rebuild their own local environment. Changing the LayerCI setup is fairly easy and I like that it is infrastructure as code so that we can validate our changes on pull requests. > > **Cons**: Sometimes it is unclear when the product has been updated. This is a rapidly developing product so sometimes we have to fix a setup after the fact to match up with the product. ----- Page: 1 / 2\ Next: [Next page](https://www.capterra.com.sg/software/202546/layerci?page=2) ## Links - [View on Capterra](https://www.capterra.com.sg/software/202546/layerci) ## This page is available in the following languages | Locale | URL | | en | | | en-AE | | | en-AU | | | en-CA | | | en-GB | | | en-IE | | | en-IL | | | en-IN | | | en-NZ | | | en-SG | | | en-ZA | | ----- ## Structured Data