NewResilience, Continuity, the Pro levels and Agentic Verification: from safekeeping to proof you can recover.The new line-up is here.See what's new
A short hero, because the routes do the work. Production's /contact opens with "How can we help you today?" and then nine options in three blocks (sales, support, careers). Most visitors arrive with one of three jobs: buying protection, getting help with an existing account, or requesting a release. The hero names those jobs, and the routes sit straight below it.
  • Book a demo stays the primary button, because most visitors to this page are prospects. Existing customers get one text link to support, so they don't have to hunt for it.
  • The ticks are confirmed facts (MESSAGING §6). Production's "in over 150 countries" is flagged in the brief, so it's left out. "3,500+ teams" is production's figure (MESSAGING §6), used unflagged as on the home page; confirm it with the other production claims.
  • Production's closing line, "Let's build bulletproof software resilience together", is gone: "bulletproof" is on the cut list.
Contact us

Talk to people who know software resilience.

Buying protection, setting up an account or requesting a release: tell us what you need and we'll put you in touch with the right specialist.

Already a customer? Go to support.

  • Trusted by 3,500+ teams
  • ISO/IEC 27001:2022 certified
  • Securing software since 2014
Social proof straight after the promise. These are the logos production already uses, loaded from codekeeper.co. Where an image can't load (for example in the preview), the name shows instead. Use the approved set only.

Trusted by 3,500+ teams, from regulated enterprises to fast-growing software vendors

Airbus Bayer European Parliament General Motors Intuit Nestlé PepsiCo Pfizer
Every route production offers, in one grid. Production's routes are kept: book a demo, chat with sales, email sales, request a callback, support (chat and email) and careers. Support gets one card that links to the support page, where its own routes live. Production has no partnerships or press contact, so neither is invented here.
  • One primary button in the grid: Book a demo. The other buttons are routes, styled as secondary.
  • Chat: in production, the "Chat with sales" button opens the HubSpot chat widget (the placeholder in the bottom corner shows where it sits). In this kit the button does nothing.
  • Email: production gives contact@codekeeper.co for sales and release requests, and service@codekeeper.co for support. Note that the kit's FAQ page uses support@codekeeper.co for termination emails and contact@codekeeper.co for support; production's /cancel and /contact-support use service@codekeeper.co. Confirm one support address and use it everywhere.
  • Release requests: the process line comes from the Trust Center FAQ, as used on the FAQ page. Operations should confirm it.

Ways to reach us

Choose the route that suits you.

Sales and support are separate teams, so your question goes to someone who can answer it.

Book a demo

A guided walkthrough on the applications you rely on: which protection fits each one, what it proves and what it costs.

Book a demo

Chat with sales

Quick answers from the sales team, live. The chat sits in the corner of every page.

Email sales

Questions about protections, pricing or an agreement. A member of the team will get back to you.

contact@codekeeper.co

Request a callback

Prefer a call? Leave your details and what it's about, and we'll call you back.

Request a callback

Support for customers

Help with your account, deposits or agreements: chat, email or book a call with the support team.

Go to support

Join the team

Interested in working at Codekeeper? See the current openings and apply online.

See open positions
Requesting a release? Email contact@codekeeper.co. We validate every request before any materials become accessible: a legal review, verification of the release condition and authentication of the beneficiary.
The contact form: production's "Request a callback", made useful for every question. Production's callback form fields weren't captured, so these are designed for routing: name, company and work email to identify the lead, a phone number for the call, and a topic that sends the request to sales, legal, support or the release team. The message is optional to keep the form short. Match the HubSpot form when this goes live, and have legal confirm the consent wording. This example sends nothing.
  • The first tick is production's own line ("Every request is handled by people with hands-on experience in software, compliance, and resilience").
  • No response time is stated: production only says "very soon". Add one if support and sales agree a standard.

Request a callback

Prefer to talk it through?

Leave your details and tell us what it's about. We'll call you back.

  • Every request is handled by people with hands-on experience in software, compliance and resilience
  • Your question goes to the right team: sales, legal or support
  • Nothing to prepare: we'll ask what we need on the call

Request a callback

Enter your name.
Enter your company.
Enter a work email, like name@company.com.
Enter a number we can call.

This is where the request would go to the team.

This is an example page, so nothing was sent. In production this form submits to HubSpot and routes the request by topic.

Real people, for warmth. Production shows the account manager Eric with a photo and a line about golf, then "Or any other Account Executive". People photography is on the keep list. Confirm before launch: that Eric still runs these conversations, that the photo is current, and that he's happy with the golf line (it's production's). The photo loads from codekeeper.co; where it can't load, the name shows instead. The kit has no person-card component, so the photo uses a small inline style for its round crop.

Talk to real people

Every request reaches a person.

Sales conversations are run by account managers who have helped secure systems like yours.

Eric, Account Manager at Codekeeper

Sales

Eric, Account Manager

Always ready to talk about golf too.

Sales

Or any other account executive

We've all helped secure systems like yours. Whoever picks up your request will know the line-up and the agreements behind it.

Addresses exactly as production states them, flagged. Production lists three regions: Europe MEA (World Trade Center, The Hague) and North America and Asia Pacific, which both show the same San Francisco address. That address is a PMB (a private mailbox). So the page says "where to find us", not "headquarters", and shows two addresses, matching the About page. Confirm before launch: both addresses, whether San Francisco also serves Asia Pacific (then say so) or whether there's a separate Asia Pacific address. Production's map image (contactus-map.webp) is left out until the regions are settled.

Where to find us

The Hague and San Francisco.

Our teams work across regions, so we can support customers wherever they're based.

Europe, Middle East and Africa

The Hague

World Trade Center The Hague
Prinses Margrietplantsoen 33
2595 AM The Hague
The Netherlands

North America

San Francisco

548 Market St. PMB 63050
San Francisco, California 94104-5401
United States

Answer the question before it becomes an email. Production's "Looking for something specific?" block, kept with the same six needs, now pointing at the rebuilt pages: choosing a plan goes to the product overview (the router) rather than straight to prices, verification goes to the proof pages, and "Read our story" becomes the FAQ, which answers more contact questions than the About page does.
The same close on every page. The contact page closes on the primary action, for visitors who scrolled past the routes without picking one. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Not sure where to start? Start with a demo.

We'll look at the applications you rely on and bring in the right specialist from there.

Chat widget goes here. Production runs HubSpot chat in this corner. Keep it on launch: it catches visitors with a quick question who won't book a demo yet. Route it to sales during office hours.