Services / Cybersecurity / Secure development

Build so fewerholes ship.

Secure code review, security checks in your CI pipeline, and builds that start from a secure default. We use “green team” as our own label for this work. Quoted after a scoping call.

Request a scoping call

In short: Ananke Digital reviews your code, adds security checks to your CI pipeline, and helps you ship builds that start from a secure default. We call this “green team” work as our own label; the term is used in more than one way in the industry, so we define it here rather than assume a shared meaning. Fees are quoted after a scoping call. Access to your repository or systems starts only after signed authorisation, a written scope and rules of engagement.

At a glance

Who it is forProduct and engineering teams that want the next release to be reviewed, and the pipeline to catch a class of problems before it ships
What we meanSecure code review, CI security checks, and secure-by-default builds. “Green team” is our label for this work.
PriceFrom US$4,500; final quote after a scoping call
Starts afterSigned authorisation, a written scope and agreed rules of engagement, where we need access to your repository, pipeline or systems
Not includedPhishing or social engineering, physical intrusion, destructive or denial-of-service testing
WhereEngineering teams we work with may be in Nairobi, elsewhere in Kenya, or overseas. The studio is in Nairobi; reviews are usually remote.
How to startStart with the scoping-call form on this page. If you prefer WhatsApp, use +254 790 939 404 — the message is prefilled “Ananke Digital: security assessment”. Or email hello@anankedigital.co.ke. We reply within one working day.

Before any access or testing: A repository, a CI system or a running preview environment is still a system we should not enter casually. When this work needs that access, it begins only after a signed authorisation, a written scope and agreed rules of engagement. A copy of a repo you send to us is covered in the scope before we review it.

What “green team” means here

Across the industry, “green team” can mean different things: sometimes a developer-security function, sometimes a training role, sometimes a label used inside a particular firm. We use it only as our own name for the three things below. If you use the term differently, we will work from this definition, written into the scope, so there is no surprise about what is being bought.

  • Secure code review. A structured review of the repository or services named in the scope: how authentication and access control are written, how data is stored and called, how secrets are handled, and how errors are exposed. You receive written findings and recommended changes, ranked by severity.
  • CI security checks. Agreed checks added to the pipeline you already use, so a class of problems can be caught when code is built or merged, not only after a release. We work with the tools you already run where we can; we do not insist on a particular vendor.
  • Secure-by-default builds. Practical defaults for new services and releases: safer configuration, less public surface, secrets kept out of the codebase, and a short standard your team can keep using after we leave.

How this sits with testing

A code review finds problems in what you are about to ship. A penetration test looks at what is already reachable from the outside. Many teams use both, in either order. Hardening and monitoring covers the running systems after a release. Live or external testing is included only when the written scope says so.

What we will not do

Secure development here is a review and a set of pipeline and default-build changes. It is not phishing or social engineering, not physical intrusion, and not destructive or denial-of-service testing. If you want the running system tested from the outside, that is a separate penetration-testing scope. We also will not claim that a review is a formal compliance certification, or that the software is free of defects once the work is done.

Pricing

Starting prices are below. The final fee is a written quote after a scoping call, and no work starts without signed authorisation, a written scope and agreed rules of engagement.

  • Secure code review: from US$4,500. Up to 20,000 lines of security-critical code.
  • DevSecOps pipeline setup: from US$8,000. Secret, dependency and code checks in one CI pipeline, tuned before any gate blocks a release.

Starting prices for the smallest sensible scope. Larger estates get a larger scope at the same rate, never a cheaper test. Prices are shown in your local currency. Prices exclude VAT where it applies.

Request a scoping call Message us on WhatsApp

Questions teams ask

What do you mean by green team?

We use “green team” as our own label for secure development work. The term is used in more than one way in the industry. Here it means secure code review, security checks in your CI pipeline, and builds that start from a secure default.

What do we actually receive?

A written review of the code or repository in scope, agreed checks added to your CI pipeline where we have access, and practical changes so new builds start from a more secure default. The exact deliverables are set in the written scope.

Do you need authorisation for a code review?

Yes, when the work needs access to your repository, pipeline or running systems. We do not begin that access until we have your signed authorisation, a written scope and agreed rules of engagement.

Will you test our live site as part of this?

Only if the written scope says so. Live testing is usually a penetration test, which is scoped separately. We do not carry out phishing, physical intrusion, or destructive or denial-of-service testing.

How is the work priced?

Starting prices are published on this page. The final fee is a written quote after a scoping call, once the systems in scope and the depth of the work are clear, and nothing starts without signed authorisation.

Testing and hardening, if you need them too

Request a scoping call

Send a short description of the repository or pipeline you want reviewed, and who can authorise access. We reply within one working day. Access waits for the signed scope.

Contact