Skip to content

Ironfang changelog

What changed across Ironfang and its products, newest first: releases, new capabilities, moved addresses and renamed products, each with its date.

  1. AddedIronfang Render

    A certified connector for Power Automate and Power Apps

    Ironfang Render is a Microsoft-certified Premium connector. Search for Ironfang Render when adding an action, connect it with an API key, and capture a screenshot, create a PDF, or start a render job and collect the file when it is ready.

    Ironfang Render

  2. AddedIronfang Render

    The Render playground covers every option, and shows what a render found

    The playground now sets lazy-content loading, success rules, custom PDF sizes, page ranges and document properties, and a page's language and clock without writing JSON, and its examples include a signed-in page, an invoice and a capture bundle. A playground result, a history record and a job each show what the page did: its status, how it settled, the language and clock it ran with, and any warnings explained.

    The playground

  3. AddedIronfang Render

    Render in another language and time zone

    locale (such as de-DE) and timezone (such as Europe/Berlin) set the browser's language and clock before the page's scripts run: date and number formatting, navigator.language, Accept-Language and local time, daylight saving included. They change what the page is told, not where the request comes from.

    Language and clock

  4. FixedIronfang Render

    A durable job no longer runs twice at once

    Since 12 October two job workers could pick up the same job at the same moment, so a job's page could be rendered twice. It was never charged twice. Each job is now taken by one worker at a time.

  5. AddedIronfang Render

    Capture bundles

    One page load, the outputs you choose: a screenshot, the rendered HTML, the page's text, Markdown and its metadata, read together and returned with a manifest of what each output is, its size and SHA-256. A bundle counts one screenshot. Also as a job, in the portal and through the MCP server.

    Capture bundles

  6. AddedIronfang Render

    Custom PDF sizes, page ranges and document properties

    PDFs take a custom page size with units (210mm, 8.5in), can let the page's own @page size decide, keep only the pages you name (1-3, 5, 8-), and carry a title, author, subject and keywords. A range that keeps no page is a 422 page_range_empty and is not charged.

    PDFs

  7. AddedIronfang Render

    Document templates

    Store a PDF template once and render it with structured JSON data: loops, conditionals and a schema the data is checked against, with an editable draft and immutable numbered revisions you publish and roll back. Each document counts one PDF. In the API and the portal.

    Document templates

  8. ChangedIronfang Render

    Durable jobs take turns between accounts

    Workers now pick the next job from the account running the fewest renders, oldest first within it, so one account's backlog no longer holds every worker while another account's job waits. Very large captures take turns too, so they cannot exhaust a browser between them.

    Jobs

  9. AddedIronfang Render

    Success rules: fail a render the page should not pass

    success_rules say what should count as a failure rather than a picture: a status such as 404 or any 5xx, a missing element, text that must or must not be on the page, or a blank capture. A render a rule fails is a 422 success_rule_failed naming the rule, and is not charged.

    Success rules

  10. AddedIronfang Render

    Full-page captures can load lazy content first

    full_page_readiness: scroll walks a full-page capture down the page before taking it, within a fixed budget, so images and sections that load as they come into view are in the picture. A capture that ran out of time or still had images loading says so in its warnings.

    Full-page readiness

  11. AddedIronfang Render

    Every render says what it found

    Renders report the page's own status and redirects, how it settled, the effective viewport and warnings such as height_capped or bot_challenge: as X-Ironfang-* headers on a synchronous render, and as diagnostics on jobs, their webhooks and request history. A 404 page captured successfully is now visibly a 404.

    Diagnostics

  12. FixedIronfang Render

    Transparent element captures and full-width capped pages

    omit_background now applies to captures of a single element, not only to whole pages. A full-page capture cut at its height cap is as wide as the page's layout, so a phone capture is no longer 1280 pixels wide.

  13. FixedIronfang Render

    Template variables are text, and a wrong type says which

    A number, boolean or object in a template's vars was refused with an unclear decoding error; it is now a 400 naming the variable and the type it got. Pass numbers as text. The TypeScript SDK 3.0.2 types vars as strings.

    Template images

  14. ChangedIronfang Analytics

    The Ironfang Analytics snippet always loads the newest release

    The install snippet now loads one address, https://analytics.ironfang.com/sdk/loader.js, which always serves the newest release, so you add it once and never change it to get a new one; a release reaches your pages within minutes. A snippet copied before today keeps working on the release it names: replace it with the one on your site's Installation tab to follow new releases.

    Docs

  15. AddedIronfang Analytics

    How far behind a live replay is, in Ironfang Analytics

    Watching a visitor live, the portal says how far behind them the picture is, such as "~2.4s behind": measured from their browser to yours, with the clocks compared through ours, and never shown more precisely than that allows. It says when the view is catching up, paused, reconnecting or stale, and you can pause it and go back to live; install snippet 0.8.0 reports the timing it needs.

    Docs

  16. AddedIronfang Analytics

    Network and error diagnostics in Ironfang Analytics sessions

    A session's Network view lists its requests with how each ended, including timeouts, aborts and answers the browser hides, and its Errors view its uncaught errors, unhandled rejections and console errors with their stacks and repeats, each linked to its moment in the replay. Each stream is a site setting, and what limits or sampling leave out is counted; install snippet 0.7.0 reports them.

    Docs

  17. ChangedIronfang Analytics

    Ironfang Analytics: every recording belongs to a session

    A site now follows sessions wherever it records, and can follow sessions without recording. Install snippet 0.6.1 records a visitor only inside their followed session, and pauseSession() keeps a page out of both.

    Docs

  18. AddedIronfang Analytics

    Sessions in Ironfang Analytics

    Every visit is now a session across all its tabs, with its journey, time on each page, uncaught errors, failed and slow requests and the moments you track, whether or not it was recorded. A session's recordings, replay and heatmap sit inside it, in the portal and the REST API; install snippet 0.6.0 reports them.

    Ironfang AnalyticsDocs

  19. AddedIronfang Security

    Continuous monitoring in Ironfang Security

    Turn on monitoring for a verified domain and Ironfang runs the External Security Check on it every week, or every day if you choose. Each check is compared with the last: new, fixed and returning findings, severity changes, newly exposed services and certificates nearing expiry are shown in the portal, and the important ones are sent by email. Up to 3 monitored domains per organisation during the preview.

    Ironfang SecurityDocs

  20. AddedIronfang Analytics

    Heatmaps in Ironfang Analytics

    See where visitors click, how far they scroll, what holds their attention and where the pointer rests on each page of your site, for desktop, tablet and mobile over the last 7, 30 or 90 days, drawn over the whole page as a real visitor saw it. They come from the recordings you already keep, with nothing more to install, in the portal and the REST API.

    Ironfang AnalyticsDocs

  21. AddedIronfang Security

    Ironfang Security: External Security Check, in preview

    Scan verified domains for DNS, TLS, HTTP security header, cookie, email authentication and exposed service issues. Each finding includes evidence and steps to fix it, and can be rechecked on its own once fixed. Free during the preview. Automated and low impact: it attempts no exploitation or logins, and it is not a penetration test or a certification.

    Ironfang SecurityCheck referenceScanner identity

  22. AddedIronfang Finance

    242 validation rules explained

    The rule reference explains 100 more rules, completing the Standard, Zero rated, Exempt, Reverse charge, Intra-community, Export and Not subject to VAT categories, the decimals rules and the Peppol exemption code pairings. Each comes with a recorded failing and corrected document.

    Rule reference

  23. RemovedIronfang Render, Ironfang Audit, Ironfang Finance

    The Renderwolf, Auditwolf and Financewolf API names are retired

    The /renderwolf, /auditwolf and /financewolf API prefixes now answer 410 Gone with the current address; use /render, /audit and /finance. Responses and webhooks carry only the X-Ironfang-* and Ironfang-* headers, MCP tools answer only to render.* and audit.*, and closing a Finance account takes DELETE FINANCE.

    Ironfang Render API

  24. RemovedIronfang Render, Ironfang Finance

    SDKs 2.0.0 drop the launch-era names

    @ironfang/render and ironfang-render 2.0.0 no longer export Renderwolf or RenderwolfError or ship the ironfang_renderwolf module; @ironfang/finance and ironfang-finance 2.0.0 drop Financewolf, FinancewolfError, ironfang_financewolf, the financewolf command and FINANCEWOLF_API_KEY. Use the Ironfang names and IRONFANG_API_KEY.

  25. DeprecatedIronfang Render, Ironfang Audit, Ironfang Finance

    Response and webhook headers are named X-Ironfang-* and Ironfang-*

    Responses carry X-Ironfang-Credits, X-Ironfang-Cache, X-Ironfang-Render-Ms and the rest, and webhooks are signed with Ironfang-Signature, Ironfang-Timestamp and Ironfang-Event-Id. The launch-era X-Renderwolf-*, X-Financewolf-* and Renderwolf-/Auditwolf-/Financewolf- headers are still sent alongside for now and will be removed; the SDKs (1.0.1), the CLI, render-action v1.2.0 and the n8n node 0.4.3 already read the new names.

    Ironfang Render API

  26. ChangedPlatform

    The MCP server is at mcp.ironfang.com

    Point MCP clients at https://mcp.ironfang.com/mcp. The server is listed in the MCP Registry as com.ironfang/ironfang; the earlier uk.ironfang/ironfang entry is deprecated.

    MCP server

  27. ChangedPlatform, Ironfang Render, Ironfang Finance

    Clients call api.ironfang.com

    New releases call the API at api.ironfang.com directly: the ironfang CLI 0.2.1, render-action v1.1.0, @ironfang/renderwolf 0.1.1, @ironfang/financewolf 0.2.1 and the n8n node 0.4.2. Upgrade older versions: HTTP clients drop the API key when they follow the redirect from api.ironfang.uk to another domain. The n8n node sends credentials saved with an ironfang.uk address to ironfang.com without any change to the workflow.

    ironfang CLIrender-action

  28. ChangedIronfang Render

    The GitHub Action is ironfang-ltd/render-action

    renderwolf-action is now render-action, v1.1.0, and @v1 points at it. Workflows that still say ironfang-ltd/renderwolf-action@v1 keep working: GitHub redirects the old name.

    render-action on GitHub

  29. ChangedPlatform

    Every service moved to ironfang.com

    The API is at api.ironfang.com, sign-in at id.ironfang.com, the portal at portal.ironfang.com and the status page at status.ironfang.com. The ironfang.uk names redirect to their ironfang.com twins for a year; API calls should move now, because a redirect to another domain does not carry the API key.

    Service status

  30. ChangedPlatform

    The website moved to ironfang.com

    Every page of ironfang.uk now lives at the same path on ironfang.com, and the old addresses redirect permanently.

  31. AddedPlatform

    The site in German and French

    Product pages, guides, the free tools, the legal pages and the Finance rule reference are published in German and French at /de and /fr, alongside English.

  32. AddedIronfang Finance

    Peppol BIS Billing 3 through the V2 API

    The V2 validation API accepts Peppol BIS Billing 3 documents, on their own engine, beside XRechnung and ZUGFeRD / Factur-X.

    V2 guide

  33. AddedIronfang Finance

    Finance SDKs 0.2.0: V2 validation

    The TypeScript and Python clients, the CLI and the GitHub Action validate XRechnung and ZUGFeRD / Factur-X through V2, as XML or PDF.

    Finance integrations

  34. AddedIronfang Finance

    ZUGFeRD / Factur-X validation, XML or PDF

    V2 validates ZUGFeRD / Factur-X 2.5.2 for the five base profiles, including hybrid PDFs: the invoice XML is extracted from the PDF and checked, and signed reports cover V2 results.

    ZUGFeRD guide

  35. AddedIronfang Finance

    142 validation rules explained

    The rule reference explains 100 more rules, including warning rules, grouped into families you can scan.

    Rule reference

  36. AddedIronfang Finance

    Free XRechnung validator and viewer

    Check an XRechnung invoice and read it as a document, in the browser, in English or German.

    XRechnung validatorXRechnung viewer

  37. AddedIronfang Analytics

    Ironfang Analytics

    Session recording and replay for your own sites, with paid plans through the portal.

    Ironfang AnalyticsDocs

  38. ChangedIronfang Render

    The free-plan badge reads Ironfang Render

    Output from a free account carries a small Ironfang Render badge; any paid plan removes it.

  39. AddedPlatform

    Articles

    Guides and notes from the team, published at /articles with an RSS feed.

    Articles

  40. ChangedPlatform, Ironfang Render, Ironfang Audit, Ironfang Finance

    API paths: /render, /audit and /finance

    Each product is served under its own name on the API. The launch-era prefixes /renderwolf, /auditwolf and /financewolf still answer as aliases.

  41. AddedPlatform, Ironfang Render, Ironfang Rig, Ironfang Audit, Ironfang Finance

    One ironfang CLI

    ironfang 0.2.0 brings render, rig (and rig connect), audit verify and finance verify into one checksummed binary for Linux, macOS and Windows.

    Releases

  42. AddedIronfang Finance

    The e-invoice rule reference

    Plain-language explanations of 42 validation rules, with a searchable catalogue and a failing example for each.

    Rule reference

  43. AddedIronfang Rig

    Rig evidence bundles

    Runs record a hash-chained event log with signed manifests and receipts, which you can download and verify offline, and hold past retention.

    Rig docs

  44. ChangedIronfang Rig

    Ironfang Test is now Ironfang Rig

    The product was renamed, with its stateful mocks and fault injection: reordering, payload mutation, connection resets, bandwidth limits and partial responses.

    Ironfang Rig

  45. ChangedPlatform, Ironfang Render, Ironfang Audit, Ironfang Finance

    Renderwolf, Auditwolf and Financewolf are Ironfang Render, Audit and Finance

    The products took the Ironfang name and their pages moved to /render, /audit and /finance. The old addresses redirect to the same page.

  46. AddedIronfang Render

    The GitHub Action

    Capture screenshots and PDFs of pages from a workflow: deploy previews, visual audits and generated images, with a table of what was captured in the job summary.

    render-action on GitHub