Skip to content
EngineerAdvisory
Menu
Design
English

Engineer / Advisory / Services

Deciding who can reach what

Accounts, passwords and permissions arranged so people hold exactly the access their job needs, and leavers lose it that day.

  1. Improved team communication and collaboration

    Improved team communication and collaboration by implementing Slack, Mattermost, 1Password, and Jira, saving 8,000 hours of labor.

    Saved ~8,000 hours by rolling out Slack, Mattermost, 1Password and Jira, turning chased information and redone work into real delivery.

  2. Automated team collaboration

    Automated team collaboration, password management, task and time management, and built a semi‑automatic project‑showcase system, raising team productivity.

    Automated collaboration, password, task and time management and built a semi-automatic project-showcase system, raising team productivity.

  3. Built Stripe and in‑app purchase entitlements

    Built the payments and entitlements layer — Stripe alongside Apple and Google in‑app purchase — gating the directory, search and export through an 11‑table access model checked on the server.

    Built the payments and entitlements layer — Stripe with Apple and Google in-app purchase — gating directory, search and export from an access model.

  4. Built company ownership claims and adjudication

    Built company ownership claims end to end — a user claims a company, an administrator adjudicates, and an approval rewrites the authorization graph that decides who is allowed to edit what.

    Built company ownership claims end to end: a user claims, an administrator adjudicates, and approval rewrites the authorization graph.

  5. Ran a continuous security scanning programme

    Established a continuous security programme — code scanning, DAST, dependency and vulnerability checks, SBOM generation, secret scanning and SHA‑pinned actions — alongside 21 written security audits.

    Established a continuous security programme — code scanning, DAST, dependency checks, SBOM, secret scanning and pinned actions — plus 21 audits.

  6. Wrote a scope rule after a credential leak

    Wrote a scope rule into the repository after a restructure carried another company's inventory, firewall allowances and prose into it — and kept the quarantined residue under the secret scanner rather than excluding it.

    The scope boundary is a written rule with a stated test, the residue is visible rather than buried, and the specific shape of credential that got through now…

Contact

Still working out what you need?

Tell us what is going wrong, or what you are trying to build. We will tell you what it would take, roughly what it would cost, and whether we are the right people for it.

From 1,400 DKK an hour, excluding VAT — and less per hour on a longer booking.

welcome@engineer.company +45 50 10 61 84 Copenhagen, Denmark