The Stack

• Next.js with static site generation (SSG)

• Cloudflare Pages for edge hosting (free tier covers everything)

• Build-time data compilation for 170+ CAD tool records

• Zero runtime database — all data is compiled into static HTML at build time

How It Works

Every page on cadguide.tools is pre-rendered HTML. When a user visits a tool page like SolidWorks or GstarCAD, they're not hitting a server that queries a database. They're getting a static HTML file served from Cloudflare's edge network — typically under 50 milliseconds, worldwide.

The trick is moving all the "dynamic" work to build time:

1. Tool data lives in TypeScript data files (type-safe, IDE-friendly)

2. At build time, generateStaticParams enumerates every possible URL

3. Sitemaps are generated as static XML routes

4. Search runs on a pre-built JSON index loaded client-side

What About Content Updates?

When we add a new tool or publish a new comparison, the workflow is:

1. Edit the data file

2. Run npm run build (a couple of minutes for 1,000+ pages)

3. Push to GitHub → Cloudflare auto-deploys

4. IndexNow API notifies Bing and Yandex of changed URLs instantly

No database migrations. No cache invalidation. No server restarts.

The Real Cost

• Hosting: $0 (Cloudflare Pages free tier)

• Domain: ~$10/year

• Page load: <50ms at the edge

The trade-off is that all content is read-only. But for a comparison directory and knowledge base, that's exactly what you want — fast, indexable, and cheap.

Free Tools, Zero Marginal Cost

We also ship 480+ free client-side engineering utilities — a DWG version checker that parses file headers locally, K-Factor sheet metal bend calculators, beam analyzers, and cross-platform shortcut matrices. Because every tool runs 100% in the browser, they cost nothing to operate at any traffic level, and they give engineers a practical reason to bookmark and link the site.

Try It

Visit CADGuide.tools and check the load time yourself. That's 1,000+ pages of content, served from the edge, for free. If you're building something similar — a directory, a knowledge base, a comparison site — the static-first approach is worth a serious look. Questions welcome in the comments.

Most online "DWG converters" and checkers require users to upload confidential engineering drawings to a remote cloud server. In aerospace, defense, and architectural engineering, uploading proprietary IP to random third-party servers is a critical compliance violation.

Here is how we implemented a 100% private, client-side DWG binary header parser in vanilla JavaScript that resolves file versions in under 5 milliseconds.

🔍 Understanding the DWG Binary Signature

AutoCAD DWG is a proprietary binary format created by Autodesk. While parsing the full 3D B-Rep entities requires complex reverse-engineered C++ libraries (like Open Design Alliance or LibreDWG), the version specification is always located in the first 6 bytes of the binary header.

Every valid AutoCAD drawing starts with a magic 6-character ASCII string:

⚡ Pure Client-Side Implementation

Instead of reading a 500MB file into memory, we use the HTML5 File.slice() API to request only the first 6 bytes:

export interface DWGVersionInfo {
  headerCode: string;
  autocadVersions: string;
  releaseYear: string;
  isModernFormat: boolean;
}

const DWG_MAP: Record<string, Omit<DWGVersionInfo, 'headerCode'>> = {
  'AC1032': { autocadVersions: 'AutoCAD 2018 - 2026', releaseYear: '2018+', isModernFormat: true },
  'AC1027': { autocadVersions: 'AutoCAD 2013 - 2017', releaseYear: '2013', isModernFormat: true },
  'AC1024': { autocadVersions: 'AutoCAD 2010 - 2012', releaseYear: '2010', isModernFormat: false },
  'AC1021': { autocadVersions: 'AutoCAD 2007 - 2009', releaseYear: '2007', isModernFormat: false },
  'AC1018': { autocadVersions: 'AutoCAD 2004 - 2006', releaseYear: '2004', isModernFormat: false },
  'AC1015': { autocadVersions: 'AutoCAD 2000 - 2002', releaseYear: '2000', isModernFormat: false },
};

export async function parseDWGHeader(file: File): Promise<DWGVersionInfo> {
  const slice = file.slice(0, 6);
  const buffer = await slice.arrayBuffer();
  const bytes = new Uint8Array(buffer);
  
  const headerCode = String.fromCharCode(...bytes);
  
  if (!DWG_MAP[headerCode]) {
    throw new Error(`Unsupported or corrupted DWG format code: ${headerCode}`);
  }
  
  return {
    headerCode,
    ...DWG_MAP[headerCode]
  };
}

The Stack

• Next.js 16 with static site generation (SSG)

• Cloudflare for edge hosting (free tier covers everything)

• Build-time SQLite for reading 240+ tool records and 104 technical guides

• Zero runtime database — all data is compiled into static HTML at build time

How It Works

Every page on cadguide.tools is pre-rendered HTML. When a user visits /tools/solidworks, they're not hitting a server that queries a database. They're getting a static HTML file served from Cloudflare's edge network — typically under 50ms worldwide.

The trick is moving all the "dynamic" work to build time:

1. Tool data lives in TypeScript data files (type-safe, IDE-friendly)

2. Guide content lives in Markdown files with frontmatter

3. At build time, generateStaticParams enumerates every possible URL

4. Sitemap is generated as static XML routes

5. Search index is a pre-built JSON file loaded client-side

What About Content Updates?

When we add a new tool or publish a new guide, the workflow is:

1. Edit the data file or add a Markdown file

2. Run npm run build (locally, ~90 seconds for 6,000+ pages)

3. Push to GitHub → Cloudflare auto-deploys

4. IndexNow API notifies Bing/Yandex of new URLs instantly

No database migrations. No cache invalidation. No server restarts.

The Real Cost

• Hosting: $0 (Cloudflare free tier)

• Domain: ~$10/year

• Build time: ~90 seconds

• Page load: &​lt;50ms at edge

The trade-off is that all content is read-only. But for a comparison directory and knowledge base, that's exactly what you want — fast, indexable, and cheap.

Try It

Visit CADGuide.tools and check the load time. That's 6,000+ pages of content, served from the edge, for free.