Skip to content

Changelog

What changed in each release, newest first.

v1.9.0

Added

  • Inbound: build a qualifying form without code (your questions, points per answer, a pass mark, who takes meetings). A qualified lead goes straight to the right person's booking page, taking turns between your people; anyone else gets a polite reply. Every lead is listed with the reason it was routed.
  • Every sequence email carries a one-click unsubscribe (the Gmail button and a small link). It adds the person to your do-not-contact list at once.
  • Follow-up emails arrive in the same Gmail conversation as the first one.
  • Subject lines can give a fallback, such as {{first_name|there}}, used when the value is unknown.
  • A/B subject lines name a winner only when a statistics test says the difference is real; otherwise the report says it is too close to call.
  • Each sequence's report shows a plain health line: healthy, worth a look, or needs fixing, with the reason.
  • A public receipt page for a claim: the exact sentence from the company's own page, the date it was read, and its fingerprint. The email composer can add these proof links.
  • Today names what changed at a watched account instead of only counting changes.

Changed

  • A follow-up waits from when the previous email was actually sent, not from when it was drafted.
  • A new look: glass sidebar and top bar, soft light, and motion that switches off for anyone who asks their device for less. Today opens with the one thing to do first.
  • The sidebar is Command, Accounts, Lists, Inbound, Sequences and Settings. Review left the sidebar; Command offers Outreach and Call prep.

v1.8.1

Fixed

  • Inside the app, the Foundry logo takes you to the app's home instead of out to the public site.

v1.8.0

Added

  • A sequence step can have two subject lines. Each person always gets the same one, and the report shows replies for each.
  • Subject lines can include the company, domain, first name or email, with a preview and a warning when a value is missing.
  • A daily sending limit for each sequence.
  • Book a call is in the header on every page.
  • Privacy and Terms pages, including how Google account data is used.

Changed

  • Pause, resume, remove and save buttons show that they are working and cannot be pressed twice.

Fixed

  • Gmail and Google Sheets show Connected only when Google still accepts the connection. If Google has ended it, the card says Expired with one Reconnect button, instead of saying Connected and failing when you send.

v1.7.1

Changed

  • A true claim whose quote was too short is no longer thrown away. If the same page states the whole claim a few words away, the claim keeps that exact sentence as its quote and says it was re-quoted. Anything the page does not state in one place is still removed.

v1.7.0

Added

  • You can book a call from the request-demo page and the footer.

Changed

  • A claim can no longer say more than the quote behind it. If it does, it is cut back to the part the quote supports, or removed with the missing words named.
  • A suggested person's responsibilities are marked unverified when no page states them.

v1.6.0

Changed

  • The home page now opens with our illustration of many pages becoming one brief. Lines draw in from each source, evidence travels into the page stack, and the brief is checked. It stays still for anyone who asks their device for less motion.
  • Further down, the receipt chain draws itself, card by card.
  • The About page now says two collaborators.

v1.5.0

Changed

  • The status check the site answers to is faster, and it still reports a database problem within seconds.
  • Releases no longer hang on the live version check: it gives up after a short wait and retries if the network blips.

Fixed

  • The real Stripe example on the home page now states the number of claims checked that its own breakdown adds up to. The earlier, larger figure could not be backed up, so it is gone.
  • Links and buttons on phones are easier to tap, and the smallest article text is a little larger.

v1.4.3

Changed

  • The Command screen has a soft glow behind the mark and the box, matching the website. Nothing else on the screen moved.
  • On a phone, the shortcuts under the Command box no longer repeat Accounts and Lists, which are already in the bottom bar.

Fixed

  • Pushing code to our repository no longer starts a deployment by itself. Only the release pipeline, with its checks and automatic rollback, puts a version live.

v1.4.2

Changed

  • The name at the top of the sidebar inside the app now says Foundry, matching the website. The default title shown when a link is shared says Foundry too.

v1.4.1

Changed

  • The Security, Governance, Pricing, About and Research pages now have an illustrated scene beside the first heading, in the same style as the home page. Each is labelled as an illustration, not product data. On a phone the scene is hidden and the text carries the page.
  • The two request pages show what happens after you send the form, using the same steps already written on those pages.

v1.4.0

Changed

  • The website's first screen is richer again. The header and the first line now say Foundry, with Oryxs shown only as the company. A product window shows an accounts list (made up, and labelled as sample data) beside a real brief from a recorded run on stripe.com, with its date and the exact quote its claim came from.
  • A new diagram shows five separate tools feeding one account record, and small illustrated scenes mark each step of the product. They move gently once and respect the reduced-motion setting.
  • The header has a soft glass look and the sections have more depth.
  • Where the site says a person is involved before anything goes out, the wording now matches the product: Foundry sends nothing until a person approves it.

v1.3.1

Added

  • A public Crawler page says what FoundryResearchBot is, how it behaves on a site, how to stop it and who to write to. The bot's identifying string now links to it, and it is in the site footer.

Changed

  • A free health check now runs every half hour and flags it if the system status or the database stops answering.
  • Small tidy-ups that change nothing you see: unused code removed from the research articles and a few screens.

Security

  • The Crawler page says plainly that when a site refuses us, or shows almost no text without JavaScript, a third-party reading service may fetch its home page and at most two other pages for us, that this request carries the service's name, and that it is not covered by our robots.txt check.

v1.3.0

Changed

  • The first screen of the website now says what Oryxs is, who it is for, what you get and why you can trust it, before the product tour. The tour follows in a clearer order: the problem, the product, the proof, how it sits beside your CRM, then how to start.
  • On a phone, the bottom bar holds the five things you use daily: Command, Accounts, Lists, Review and Sequences. Settings moved to a gear at the top, and phones now have an Account tab, so you can sign out.
  • Moving from a list to a sequence now works fully from the keyboard. Focus lands where you expect, and Escape takes you back to the button you started from. The sequence tabs respond to the arrow keys, and Search keeps focus inside it.
  • The sequence and receipt pages show a loading state instead of a blank screen, and a missing sequence says so with a link back. Today now has a Try again button if it fails to load.
  • The system status check now also confirms the database is answering, and a release rolls back by itself if it is not.

Security

  • When Oryxs reads a company's public pages it now says who it is, with a contact address, and no longer presents itself as a browser. It respects each site's robots rules for that name and waits between requests to the same site.
  • Most errors now have the same plain shape and a reference number, and technical detail from inside the system is kept out of what you see.
  • Oversized requests are refused. Sign-in and other sensitive actions are rate limited.
  • If a send or an enrolment is repeated after the first one has finished, for example by a retry, it no longer creates a duplicate.
  • A security.txt file now tells researchers where to report a problem.
  • One library used for reading pages was updated to clear four newly published advisories, and our audit reports nothing open.

v1.2.0

Added

  • A sample CRM, so you can try the whole journey without connecting your own. Choose "Use the sample CRM" on Accounts, or "Explore with sample data" when you start. Its companies and people are made up, every one is labelled as sample data, and you can remove them all in one step.
  • Companies and leads from the sample CRM go into lists and into the "who would start, who is skipped" preview exactly as they do from HubSpot, including the reasons, such as no email on record or no website on file.

Changed

  • Sample companies are never researched and nothing is ever sent to a sample person, so trying it costs nothing and sends nothing.
  • Every release now runs the same journey on the rehearsal copy first, using the sample CRM, so a break in it is caught before it reaches you.

Fixed

  • Releases no longer depend on downloading a font during the build: the typeface is now stored with the product, so a slow or unreachable font server can no longer stop a release.
  • The database check that runs before a release no longer mistakes a dropped connection for a missing table.
  • The status check that tells you whether Foundry is working no longer errors.

Security

  • An independent review of the sample CRM closed several ways around its rules: unusual spellings of a sample address, a sample address typed into chat, watching a sample account, emailing a sample address, and pushing sample people into a real CRM. All are now refused before anything is spent or sent.

v1.1.0

Added

  • A public "What's new" page that lists every release in plain language, and the version number shown in the footer and in your account menu.
  • Standard browser security headers on every page.

Changed

  • Every release now goes through a rehearsal on a private address first. It reaches your domain only after the checks pass, and it rolls back by itself if a check fails afterwards.

Security

  • Updated the libraries we depend on, in the backend and in the web app, so that our vulnerability audit now reports nothing open.
  • New automatic checks before each release: secrets in the code, known vulnerabilities, software licences, honest wording on the public pages, and the rules about not using anyone else's code or data.

v1.0.0

Added

  • The Command home, with a switcher for the model that answers.
  • Runs that keep going while you move around the app, and show in your history from the start.
  • HubSpot companies and leads, read into Foundry.
  • Lists of companies and people, with a Lists entry in the rail.
  • Adding a list to a sequence, with a preview of who would start and who would be skipped, and why.
  • People on every account, each with where we found them.
  • Emails addressed to a named person, in one exact format: a subject, a greeting by first name, a short body, one sign-off and your name and company.
  • Sequences rebuilt as Steps, Prospects, Settings and Report, with editable waits and a preview of each step for each person.
  • A public trust centre: Security and Governance, each claim next to the check behind it, and a plain list of what is not done yet.

Changed

  • The whole product and the public site are now one calm design, white and light only.
  • Long lists and account tables load with far fewer database reads and draw the first 100 rows, with a button to show more.

Fixed

  • Keyboard focus is now clearly visible on every signed-in screen.
  • Buttons and links on phones and tablets are at least 40 pixels tall.
  • The primary button's text now has enough contrast.
  • On a phone, a run under way now shows above the tools instead of a screen below.
  • Add people now moves focus into the panel, closes with Escape and returns focus afterwards.
  • Today now finds briefs that sit behind newer messages.

Security

  • Fifteen fixes from a review of the new routes, each with a test.
  • A send could carry a second recipient that skipped the do-not-contact check. One valid address is now enforced.
  • A line break in a subject or address is refused up front instead of failing deep in the mail code.
  • The HubSpot cache is no longer shared between two users of one team, or kept after a token changes.
  • Reads from HubSpot are rate limited per team, and paging cursors are checked.
  • Adding a lead to a list now trusts only what HubSpot returned, not the browser's copy.
  • Names, titles and list names drop hidden control characters.
  • Error messages when HubSpot cannot be reached no longer show raw connection details.
  • Database reads now page through the 1,000-row limit instead of silently dropping rows beyond it.

Rather talk it through with a person?

Book a call