About Haivix

Technical tools built by people solving real problems — not a generic free-tools directory.

Haivix publishes browser-first utilities for IT administrators, developers, and everyday document work. Our deepest investment is in networking and developer workbenches, plus privacy-conscious PDF and data tools — each documented to match what the implementation actually does.

How Haivix tools are built

The site is a static HTML/CSS/JavaScript application deployed on Cloudflare Pages. Tool behavior lives in modular ES modules under assets/js/tools/. A shared registry lazy-loads the right module for each page. SEO copy for flagship tools is authored in structured data files and rendered by generators — we do not hand-edit hundreds of duplicate tool pages.

  • Browser-local engines — PDF, image, text, converter, and many developer tools run entirely in your browser.
  • Cloudflare Workers — Some PDF/Office conversions and AI tools use Haivix API endpoints when browser-only processing is not enough.

How we test tools

Before deployment we run registry verification, link and SEO audits, unit tests for critical engines, and Playwright end-to-end checks for high-risk workflows (PDF tools, network utilities, developer tools). Tool page claims are written to align with the code path — not generic SEO templates repeated across the catalog.

Browser-local vs server-processed

Every tool page states how your input is handled. Most file workflows never leave your device. Server-assisted tools disclose when Haivix infrastructure or a third-party resolver (for example Cloudflare DNS-over-HTTPS) receives data. See our Privacy Policy and Cookie Policy for advertising, analytics, and AI processing details.

How technical information is verified

Developer and networking tools reference common standards (JSON, CSV, DNS, CIDR) while documenting browser limitations explicitly. Treat every export or generated artifact as a starting point and validate it in a representative environment before production rollout.

Editorial policy

  • Flagship tool pages receive unique, implementation-aligned copy; the long tail stays short and honest rather than padded with duplicate SEO text.
  • Blog articles focus on workflows tied to real Haivix tools — not bulk rewritten explainers.
  • We do not publish guaranteed outcomes for AI, finance, or tax results.

Report incorrect results

Found a wrong calculation, misleading explanation, or broken workflow? Email hello@haivix.com with the tool name, what you expected, what happened, and any sample input you can share safely. We prioritize fixes that affect correctness or privacy disclosures.

Third-party software and source

Some tools load open-source libraries from a CDN or from Haivix R2. The video speed changer uses FFmpeg.wasm (@ffmpeg/core 0.12.10) and libx264 under their respective licenses. Source is available upstream:

For a source copy of the exact FFmpeg.wasm build used by the speed changer, email hello@haivix.com.

Security and privacy principles

  • No unnecessary sign-ups for core tools.
  • Clear disclosure before data leaves the browser.
  • No selling of tool input content.

Implementation-first docs

Page copy describes what the JavaScript actually does — including limits and honest "when not to use it" guidance.

IT depth where it matters

Networking and endpoint tools get the same rigor we expect from internal runbooks.

Privacy by workflow

Browser-local where possible; explicit server or AI processing where not.

Measured publishing

Quality guides and flagship pages over mass-produced templated content.

Explore the workbench tools

Start with network lookups, subnet math, or the developer utilities you use every day.