Automate everything. Ship with confidence.
Powerful CI/CD pipelines defined in code. GitHub Actions-compatible syntax means you can migrate easily. Secure runners, encrypted secrets, and comprehensive logs.
Workflows in YAML
Define your pipelines in familiar syntax. If you know GitHub Actions, you already know Repolaris CI.
Triggers
Push
On every push to specified branches
Pull request
When PRs are opened, updated, or merged
Schedule
Cron-based scheduling for recurring tasks
Manual
Trigger workflows with inputs via UI or API
Webhook
Start workflows from external events
Tag
Run on new tags for release automation
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- run: npm test
build:
needs: test
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run buildjobs:
test:
strategy:
matrix:
os: [ubuntu-latest, macos-latest]
node: [18, 20, 22]
fail-fast: false
runs-on: ${{ matrix.os }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node }}
- run: npm testMatrix builds
Run jobs across multiple configurations automatically. Test against different OS versions, language versions, or any combination of variables.
- Include/exclude: Add or remove specific combinations
- Fail-fast: Stop all jobs if one fails, or let them complete
- Max parallel: Limit concurrent jobs for resource management
Flexible runners
Managed Runners
- Linux: Ubuntu-based with common tools pre-installed
- Ephemeral: Fresh environment for every job
- Secure: Isolated containers prevent cross-job contamination
- Fast startup: Jobs start in seconds, not minutes
Self-Hosted Runners
- Full control: Your hardware, your network, your rules
- Specialized hardware: GPU, ARM, or custom configurations
- Network access: Reach internal services without exposure
- Air-gapped: Run in isolated environments (Enterprise)
Secure secrets
Encrypted Storage
AES-256-GCM encryption
Industry-standard encryption at rest
Access controls
Limit which workflows can access which secrets
Masked output
Secrets are automatically masked in logs
Scope Levels
Repository secrets
Available to all workflows in a repo
Organization secrets
Shared across repos in an org
Environment secrets
Scoped to specific deployment environments
Artifacts & logs
Artifacts
Upload artifacts
Save build results, test reports, binaries
Download artifacts
Access in later jobs or after completion
Retention policies
Automatic cleanup after configured period
Artifact browser
Download via web UI
Logs
Real-time streaming
Watch logs as jobs run
Persistent storage
Access logs after completion
Structured format
Parse logs programmatically
Search and filter
Find what you need in large logs
PR integration
CI results appear directly in pull requests.
- Required checks: Block merge until CI passes
- Status indicators: Clear pass/fail/pending states
- Log links: Jump directly to job logs
- Re-run controls: Retry failed jobs without new push
All checks passed
How we compare
| Feature | Repolaris | GitHub | GitLab | CircleCI |
|---|---|---|---|---|
| YAML config | ||||
| Matrix builds | ||||
| Job dependencies | ||||
| Encrypted secrets | ||||
| Environment approvals | — | |||
| Self-hosted runners | ||||
| Integrated Git hosting | — | |||
| EU data residency | — | — |
CI/CD included in all paid plans
| Plan | Included Minutes | Parallel Jobs | Retention |
|---|---|---|---|
| Free | 500/month | 2 | 7 days |
| Teams | 5,000/month | 10 | 30 days |
| Enterprise | Custom | Custom | Custom |