CicdExpress
Get started

Menu

Services Solutions How it works Pricing About Contact

More

FAQ Log in
Start now
Process

From kickoff to green build, step by step.

Transparent process. No meetings unless you want one. Every engagement runs the same six steps — here's exactly what happens from the moment you click "Get started."

  1. 01

    Pick a plan

    Minute 1

    Choose the tier that matches your pipeline complexity. One-time payment via Authorize.Net — no subscription, no surprise charges down the line.

    • Starter, Basic, Pro, or Enterprise
    • Pay with card — card details never stored on our side
    • Instant account creation
  2. 02

    Grant repository access

    Same day

    We need read/write access on the repo so we can push the branch with the pipeline. For GitHub that's usually a collaborator invite; for GitLab it's a Maintainer role on the project.

    • GitHub collaborator invite (Write role)
    • GitLab project Maintainer role
    • Bitbucket repository write access (Pro / Enterprise)
  3. 03

    Share intake details

    Same day

    Fill out the secure intake form on your order page — tech stack, deploy target, environment variables, deploy credentials. Credentials are encrypted in our database and only visible to the engineer assigned to your order.

    • Repo URL + default branch
    • Tech stack (languages, frameworks, DB)
    • Deploy target (VPS, AWS, Kubernetes, etc.)
    • Environment variables (encrypted)
  4. 04

    We engineer the pipeline

    1 – 4 days

    We write the workflow file(s) tuned to your stack, wire secrets into your provider's secrets store, cache dependencies correctly, and iterate until every stage runs green against the real state of your repo.

    • Workflow authored on a feature branch
    • Secrets configured in GitHub / GitLab
    • Caching tuned per package manager
    • Jobs optimised for speed and reliability
  5. 05

    Test & iterate

    Until it's green

    We run the pipeline against your actual code — not a template. If your tests fail for reasons unrelated to CI, we'll flag them in the order chat. If they fail because of the pipeline itself, we fix it before you see it.

    • Full run executed on our side first
    • Issues triaged in the order chat
    • No delivery until the pipeline is fully green
  6. 06

    Delivery — PR + docs + proof

    Day of completion

    You get a pull request with the pipeline files, a documentation update in your README, and in the PR body a link to the passing run plus a screenshot. Review, merge, ship.

    • .github/workflows or .gitlab-ci.yml
    • docs/CI.md with plain-English explanation
    • Link + screenshot of the green run
    • Ongoing chat available for follow-up questions
Expectations

What you can count on.

Typical delivery: 2–5 business days

Starter and Basic usually land in 2 business days. Pro takes 2–4 days. Enterprise takes 3–5 depending on complexity.

We touch your repo, not your cloud

Deploy credentials stay in your provider's secrets store. We configure them, we don't keep them. Credentials in our DB are encrypted at rest.

Not green? Not delivered.

We don't hand off a half-working pipeline. If we can't deliver a green build for your project, we refund in full — see the refund policy.

Step one starts here.

Pick a plan and we'll meet you in the order chat.

See pricing Read the FAQ