Skip to content
EngineerSoftware
Menu
Design
English

Engineer / Software / 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. Built organization context switching for users

    Designed an organization context‑switching system with client localStorage and server‑side cookie mirroring, letting users act as managed organizations while enforcing least‑privilege authorization.

    Built organization context-switching with localStorage and server cookie mirroring, letting users act as managed orgs under least-privilege auth.

  2. Built email with failover and delivery logging

    Built email as a platform capability — three providers with failover, delivery webhooks, send and delivery logging, templating and campaigns — behind a startup check that will not boot without one.

    Built email as a platform capability: three providers with failover, delivery webhooks, send and delivery logging, templating and campaign broadcasts.

  3. Hardened the application with nonce‑based CSP

    Hardened the application with nonce‑based CSP, HSTS, SameSite cookies, least‑privilege database roles and server‑side entitlement re‑checks.

    Hardened the app with nonce-based CSP, HSTS, SameSite cookies, least-privilege database roles and server-side entitlement re-checks.

  4. 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.

  5. Built fail‑closed rate limiting and anti‑abuse

    Built fail‑closed abuse controls — 22 Redis‑backed rate limiters, Cloudflare Turnstile, request idempotency and an origin lock — so the platform sheds bots and floods instead of trusting its callers.

    Built fail-closed abuse controls: 22 Redis-backed rate limiters, Cloudflare Turnstile, request idempotency and an origin lock on the front door.

  6. 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.

  7. Reached the unused half of the core

    Reached the half of the messaging core the application had never used — backup transfer, disappearing messages, message editing and resending, verified invitations, proxies and encryption policy — driving every test against the real library with no mocks.

    The previously unreached half of the core is driven by tests against the real library, and the wrapper carries the highest floor in the project.

  8. Published a readable Tor onion mirror

    Published the site as a Tor onion mirror on a readable address beginning engineer, with the key generated off the host so it never reached this repository or a laptop, and left it the one front door of four that is never counted.

    The site has four front doors onto one build, and this is the only one that is never counted. Gemini requests and Gopher connections are tallied per day with…

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