About Wardline

One question.

One minute.
Two cloud engineers at a dark wall display, one pointing at a magenta branch of a storage graph
Mara Lindqvist at a dark desk, soft magenta screen light on one side of her face, a node graph out of focus behind her

Mara Lindqvist, co-founder and CTO. Sample person.

Sample map, account prod-⁠eu
12,406 grants
3 hops · 38 minutes · Read-only
§1   Story

An auditor asked who could read one bucket.

For six years Mara Lindqvist answered that question by hand. Each year it took a week, because the facts lived in four different consoles and nobody could see how they joined up.

Daniel Roth had spent a decade running platform engineering at a payments company, and he had the same problem from the other side. The two of them drew the first map on a whiteboard: every identity, every role, and the few paths that ended somewhere that mattered.

Wardline still does that one job. It reads your cloud without changing it and shows you what can reach your data.

Engineer's hands at a keyboard in front of a dark identity graph, a hardware security key on the desk
38 min

to find three hops nobody had drawn. Sample data.

§2   Timeline

Six entries, one job.

2021

Two founders, one bucket

Mara Lindqvist, Daniel Roth

The first map is a whiteboard. It shows one bucket and everyone who can reach it.

2022

The read-only role

Temi Adeyemi joins

A short template anyone can check line by line. No agents, and one delete removes it.

2023

Pipelines on the map

Minh Tran joins

Deploy tokens and build roles go on the map, and the short paths start showing up.

2024

Three clouds, one vocabulary

Hana Mori joins

AWS, Microsoft Entra ID and Google Cloud read as one set of identities and roles.

2025

Fixes as pull requests

Arjun Nair joins

Small Terraform changes replace tickets, and a named engineer joins every customer channel.

2026

The hourly map

Team plan

The map updates every hour, so a new path shows up the day it appears.

§3   Principles

Four ruleswe build by.

§3.1

Read, never write.

Your first map runs on one read-only role. Nothing is installed and nothing in your cloud changes.

§3.2

Rank by reach.

A path counts by what it ends at. A dull setting three hops from customer records goes first.

§3.3

Name the engineer.

Every customer gets one of our engineers in a shared channel, on working hours, from the first map on.

§3.4

Leave easily.

One delete removes our access. If we are not useful, leaving should take less time than joining.

§4   Team

Engineers, not account managers.

Six leads, each with a named specialism. The person who reads your first map is the person in your channel afterwards.

A named engineer, not a ticket queue. Everyone here has a page and a record of what they work on.

Talk to an engineer

Free for one account. No card and no sales call.