https://gitlab-pipelines.puzl.cloud puzl.cloud * Sign In * Sign Up Run your GitLab pipelines faster and cheaper Forget cloud instances! Focus on CI/CD workflows while we handle your GitLab runners and pipeline jobs. Start Free Trial tanuki-in-space stars Puzl's pipeline jobs beat ordinary cloud instances due to burstable compute resources: only pure resource consumption is paid. See pricing up to 2x faster^* up to 5x cheaper^* ^* Comparison based on the benchmarks below against GitLab.com SaaS runners. Each pipeline job is boosted with wide CPU and memory limits, but only real usage counts. CPU usage Memory usage Effective momentary spending on Puzl Job resource limits on other platforms Ineffective constant spending Job resource limits on Puzl CPU usage Memory usage Effective momentary spending on Puzl $0.0045$0.0001$0.035$0.025$0.0001$0.0023 Cloning repository Launching build Packing Docker image * The chart depicts a hypothetical pipeline job containing typical stages. Job runtime Do not pay for the resource limits during idle time. Puzl counts cpu-seconds and memory GB-seconds only when your job is actually utilising them. Puzl is made for engineers by engineers. We know how important the performance metrics are. Here is the comparison of Puzl pipeline jobs against other platforms in various benchmarks. Building Material UI components library puzl.cloud Startup 4m 51s | $0.0939 Growth 4m 21s | $0.0738 Growth +cache 2m 49s | $0.0501 Business 4m 21s | $0.0287 Business +cache 2m 36s | $0.0192 GitLab.com SaaS Runners 4 vCPU 16 GB 6m 30s | $0.13 4 vCPU 16 GB +cache 5m 30s | $0.1101 8 vCPU 32 GB 5m 6s | $0.153 8 vCPU 32 GB +cache 3m 53s | $0.1167 Digital Ocean Droplet 4 vCPU 8 GB 11m 13s | $0.0714 Building Linux Kernel puzl.cloud Startup 4m 30s | $0.0893 Growth 2m 49s | $0.0634 Business 2m 22s | $0.0254 GitLab.com SaaS Runners 4 vCPU 16 GB 8m 2s | $0.1606 8 vCPU 32 GB 4m 29s | $0.1343 Digital Ocean Droplet 4 vCPU 8 GB 10m 49s | $0.0714 Building WordPress Docker image puzl.cloud Startup 2m 19s | $0.0141 Growth 2m 19s | $0.012 Business 2m 19s | $0.0047 GitLab.com SaaS Runners 4 vCPU 16 GB 2m 36s | $0.052 8 vCPU 32 GB 2m 36s | $0.0775 Digital Ocean Droplet 4 vCPU 8 GB 4m 7s | $0.0714 * Results of all platforms may vary based on factors such as network activity, package registry availability, and more. * For Digital Ocean Droplet benchmarks, the official GitLab Docker Machine executor was used. tanuki-waving-goodbye-to-vendor-lock stars Say goodbye to platform lock-in! The transition from your current runners requires no additional settings in your pipelines. If unsatisfied, you can quickly switch to other GitLab runner options. Security and speed are not a trade-off Each pipeline job operates within its own light-weight virtual machine, booting up in a few seconds. Puzl is an efficient execution layer, designed to speed up and scale your pipelines without requiring DevSecOps expertise. Choose your optimal Resource Package Each Resource Package is valid for 1 year. If included resources run out, additional charges will be applied on a per-second basis, based on the package's rate. Startup $69.00 1 year access to the service CPU 12,000 vCPU-minutes included 6 vCPU per pipeline job $0.00007 per vCPU-second after exhaustion Memory 48,000 GB-minutes included 16 GB per pipeline job $0.00001 per GB-second after exhaustion IOPS Optimized File System 25 GB per pipeline job Included features Manage your runners via dashboard or declarative API Each pipeline job is running in its own isolated virtual machine 1 runner 5 concurrent pipeline jobs per runner Up to 2 services per pipeline job Community support in Discord Growth $349.00 1 year access to the service CPU 75,000 vCPU-minutes included 12 vCPU per pipeline job $0.00005 per vCPU-second after exhaustion Memory 300,000 GB-minutes included 48 GB per pipeline job $0.000007 per GB-second after exhaustion IOPS Optimized File System 40 GB per pipeline job Flexible Cloud Storage 10 GB included $0.00000007 per GB-second for usage beyond Nvidia A100 (40GB) 2 GPU per pipeline job $0.0005 per allocated GPU-second Included features Manage your runners via dashboard or declarative API Each pipeline job is running in its own isolated virtual machine 5 runners 15 concurrent pipeline jobs per runner Up to 4 services per pipeline job Pre-configured pipeline job cache and persistent data storage Each runner's data storage is isolated and might be accessed like a normal S3 bucket 8/5 support, 1 business day response time Business $1,449.00 1 year access to the service CPU 800,000 vCPU-minutes included up to 32 vCPU per pipeline job $0.00002 per vCPU-second after exhaustion Memory 3,200,000 GB-minutes included up to 256 GB per pipeline job $0.0000025 per GB-second after exhaustion IOPS Optimized File System 64 GB per pipeline job Flexible Cloud Storage 50 GB included $0.00000005 per GB-second for usage beyond Nvidia A100 (40GB) up to 4 GPU per pipeline job $0.0004 per allocated GPU-second Included features Manage your runners via dashboard or declarative API Each pipeline job is running in its own isolated virtual machine 5 GitLab integrations (use them to isolate different teams or GitLab instances) 10 runners per GitLab integration 30 concurrent pipeline jobs per runner Up to 10 services per pipeline job Pre-configured pipeline job cache and persistent data storage Each runner's data storage is isolated and might be accessed like a normal S3 bucket GitLab interactive web terminal 8/7 support, 24 hours response time Coming Later Restrict the list of Docker images that can be used in .gitlab-ci.yml Local Docker registry cache for even faster pipeline job start Metrics of resource consumption by each pipeline job Set quotas for resources per GitLab integration or runner MS Windows execution environment ARM execution environment Enterprise By Request 1 year access to the service Contact Us Included features Your runners and pipeline jobs running on dedicated nodes for extra isolation Your runners and pipeline jobs running within dedicated control plane for extra isolation Custom requirements: ARM, Intel, GPUs other than A100, etc. Run pipeline jobs on your own infrastructure while managing runners in Puzl Servers located in the regions other than EU Custom Linux kernel build for specific pipeline jobs Each package comes with 14-day free trial Trial includes 200 vCPU-minutes and 800 GB-minutes of memory. We ask for your credit card solely to minimize fraud risk. Feel free to cancel your trial anytime. For bank transfer options, please contact us. Start Free Trial Get started * Get Started * Create Account * Apply Trial * Create GitLab Runner Choose your option I use GitLab.comI use self-hosted GitLab Have questions? I am located in the EU. How does EU location affect pricing and VAT application? All prices do not include EU VAT. If you're located in the EU: 1. All prices above are listed in USD, but for EU residents, the prices are the same numbers in EUR. 2. Puzl Cloud is required to charge VAT on sales of electronic services to non-business customers (B2C) in the EU. 3. Puzl Cloud is required to charge VAT on sales of electronic services to business customers (B2B) in Estonia. 4. Puzl Cloud charges local VAT, unless you have a valid Registration Number associated with VAT. 5. All VAT collected from customers will be reported to the local tax authorities under the EU simplified VAT registration regime known as the Mini One Stop Shop ("MOSS"). What execution environments do you support? Currently, we support only Linux x86-64bit environment for executing pipeline jobs. Can I run Docker within Puzl's GitLab pipelines? Yes. The service is optimized to run Docker out of the box without requiring any changes in your .gitlab-ci.yml. Are pipeline jobs running in an isolated kernel? Yes, all pipeline jobs run in an isolated kernel, ensuring both security and performance. What kind of CPU cores are allocated for pipeline jobs? By default, we allocate shared CPU cores for pipeline jobs. However, if you opt for the Business or Enterprise packages, you have the flexibility to request exclusive CPU cores. Do note that when exclusive CPU cores are allocated, they are billed based on the requested allocation, irrespective of momentary usage. What settings do I need to make in my pipelines to run them on Puzl? No changes are required in your existing .gitlab-ci.yml files. Puzl is fully compatible with your existing pipelines regardless of the GitLab runner executor you currently use. Is it possible to use GPUs in my GitLab pipelines? Yes, you can request Nvidia A100 GPUs for specific pipeline jobs if needed. This feature is available in all our Resource Packages, except for the Startup package. Please note that GPU-seconds are not included in the packages and will incur additional charges. Do you support any pipelines other than GitLab? Currently, we only support GitLab pipelines. However, support for other pipelines is in our roadmap. If you have a specific CI/CD platform or engine in mind or are keen on seeing support for a particular one, please let us know. Your feedback might influence our priority list! Is Puzl related to GitLab Inc.? No, Puzl operates independently of GitLab Inc. "GitLab" is a registered trademark of GitLab Inc., and we use it with the proper acknowledgment. Not sure yet? Ask on Discord! * Documentation * Cookie Policy * Privacy Policy * Terms * GitLab Pipelines Terms of Use visamastercardamerican-expresssepaswiftgoogle-payapple-pay cartes-bancairesunion-paydiscover nvidia partner (c) GPU Computing OU, 2023 Harju maakond, Tallinn, Kesklinna linnaosa, Rotermanni tn 6, 10111 Estonia Company code 14476114 VAT number EE102212851