FAQ   21 questions

Ask beforeyou connect.

These are the questions teams ask before they add the role. If yours is missing, an engineer will answer it.

§1
Before you connect
6 questions
§2
What we read
5 questions
§3
Price and paperwork
4 questions
§4
Fixes and reports
6 questions
§1   Before you connect

Is this the right first step?

What does a map give us that a settings scanner does not?

A scanner lists settings that break a rule. A map shows what each one connects to, so you start with the path that ends at real data.

Which account should we connect first?

The one closest to your customer data. If you are not sure, pick your busiest production account. One account is enough for a useful first map.

Who reads the map with us?

One of our engineers, in a shared channel, on working hours. The person who reads your first map stays with you afterwards.

Can it affect production?

No. The role only lists and describes settings. Nothing is installed and nothing runs inside your workloads.

Who has to agree on our side?

One person with access to the account adds the role. Most teams show the template to their cloud lead first, and it is short enough to check line by line.

How soon can we start?

Today. Add the role at minute 0 and read the map at minute 40.

§2   What we read

Settings,never contents.

What does the read-only role allow?

It can list and describe settings. It cannot change anything, and it cannot open files or read records.

Do you copy our data?

No. We read names, tags, roles and policies. File contents and customer records stay where they are.

Which clouds and tools do you read?

AWS, Microsoft Azure and Google Cloud, along with GitHub Actions, GitLab CI, Terraform and the Kubernetes clusters tied to them.

Do we install anything?

No. There are no agents and nothing is added to your workloads. You add one role.

How do we remove your access?

Delete the role. Our access ends at that moment, and you need nobody's permission.

Engineer's hands at a keyboard in front of a dark identity graph, a hardware security key on the desk
§3   Price and paperwork

Priced per account.

How is the price set?

Per cloud account. Team is a sample $480 per cloud account, per month, however many people read the map.

What counts as a cloud account?

One AWS account, one Azure subscription or one Google Cloud project. Pipelines and Kubernetes clusters tied to it are included.

Will you sign an NDA?

Yes, before the first call if you want. Our own outside review summary is shared under NDA too.

Can we see your SOC 2 report?

A real vendor should show you one. Wardline is a fictional business, so its Type II report is a demo sample and nothing here has been audited.

The three plans
First Map
$0, one account, one time
Team
$480 per account, per month
Company
Ask us, 50 accounts or more
Sample prices.
§4   Fixes and reports

What you get after the map.

Day 7

The first pull requests arrive on the Team plan. Each one fixes one root cause.

What is in the report?

Six sections: a summary for your board, accounts and settings read, paths ranked by reach, who could reach what by date, fixes merged, and exceptions with their owners. Reports come with Team and Company.

How do you rank paths?

By what they reach, not by how many settings they break. A dull setting three hops from customer records goes first.

Which frameworks does it map to?

CIS Benchmarks, SOC 2 and ISO/IEC 27001. Each has a set place in the report, so your auditor can find it without asking.

How do fixes reach us?

On the Team plan, as small Terraform pull requests, one root cause each, with a note on how to roll back.

Who merges them?

Your engineers, the usual way, in your own repositories. Nothing merges without them.

What about paths we choose to keep?

Each one gets a named owner on your side and stays in the report as an exception.

Not answered here?

Ask an engineer.

Arjun Nair working at a laptop and a portable dark monitor showing a graph with one magenta path