4.2M
Pages Archived
892K
HTML Documents
340K
GIF Animations
99.97%
Uptime
~12ms
Avg Latency
// System Architecture

How It Works

A four-layer architecture designed for massive-scale archival with fault-tolerant storage and lightning-fast retrieval.

Client
Web App (React)
REST API
GraphQL
CLI Tool
SDK (Python/Node)
API Gateway
Load Balancer
Auth Service
Rate Limiter
API Router
Request Logger
Processing
Crawler Engine
Parser Pipeline
Indexer
Renderer
OCR Module
Hash Verification
Storage
WASM Object Store
Elasticsearch
Redis Cache
PostgreSQL
CDN (CloudFront)
IPFS Gateway
// Technology Stack

Core Technologies

We've carefully selected each technology to balance performance, reliability, and the unique demands of archival science.

🕷️

Crawler Engine

v4.1.0

Custom-built distributed crawler optimized for 90s-era HTML, handling frames, tables, and early JavaScript with 99.2% capture accuracy.

Rust Tokio reqwest HTML5lib
🔍

Search Engine

v2.8.3

Fine-tuned Elasticsearch cluster with era-specific tokenization, supporting semantic search across 4.2M documents in under 50ms.

Elasticsearch OpenSearch BM25 Vector DB
🗄️

WASM Object Store

v3.0.1

Write-Once Read-Many immutable object storage built on S3-compatible infrastructure with cryptographic integrity verification for every archived asset.

S3 Glacier SHA-256 CAR Files
🎨

Retro Renderer

v1.5.2

Pixel-perfect rendering engine that faithfully reproduces Netscape 3.0, IE 4.0, and early web layouts using headless browser technology with custom style engines.

Puppeteer Playwright Canvas MIME Parser

API Gateway

v5.2.0

High-throughput API layer handling 12,000+ requests per second with built-in rate limiting, authentication, and request/response caching.

Kong GraphQL gRPC Redis
📊

Monitoring & O11y

v3.1.0

Comprehensive observability stack tracking crawl health, storage integrity, API performance, and archival completeness in real-time.

Prometheus Grafana Jaeger Loki

From URL to Archive

Every page goes through a rigorous seven-step pipeline ensuring complete and faithful preservation.

1

URL Discovery

Seed URLs are ingested from web rings, directories, and user submissions

2

Deduplication

Content hashes prevent redundant crawls of already-archived pages

3

Fetch & Capture

Full page content, assets, and metadata are fetched and snapshot

4

Parse & Extract

DOM parsing extracts links, text, and structured metadata

5

Verify & Sign

Cryptographic signature ensures archival integrity

6

Index & Store

Indexed for search and stored in WASM with IPFS replication

7

Serve & CDN

Published globally via CDN with retro rendering on-demand

// Developer API

Simple Integration

Interact with our archive programmatically using our REST API or one of our official SDKs.

search.py
import webarchive # Initialize client client = webarchive.Client( api_key="wa_live_..." ) # Search archived pages results = client.search( query="geocities personal homepage", era="1995-1999", format="html", limit=50 ) for page in results: print(page.url, page.archived_at) # Restore the original HTML content = page.restore()
archive.sh
# Archive a URL via CLI wa-cli archive \ --url "https://geocities.com/~cooluser" \ --date "1997-03-15" \ --depth 3 \ --verify # Output: [✓] Page captured successfully [✓] 24 assets preserved [✓] SHA-256 verified [✓] Archived at 1997-03-15T00:00:00Z ID: wa_arc_8f3d2a1b
// API Reference

Key Endpoints

Explore the core API endpoints for interacting with the archive.

GET
/v2/archive/search

Search archived pages with era filters, format constraints, and semantic matching. Returns paginated results with metadata.

GET
/v2/archive/:id/restore

Retrieve a fully restored version of an archived page, rendered in its original context with all assets.

POST
/v2/archive/crawl

Submit a URL for archival capture. Supports depth configuration, schedule, and notification webhooks.

GET
/v2/archive/timeline

Get chronological snapshots of a specific URL over time, showing how pages evolved across years.

GET GET
/v2/stats/analytics

Retrieve aggregate statistics: archive size, crawl rates, format distribution, and preservation metrics.

DELETE
/v2/archive/:id

Request archival removal under DMCA or privacy concerns. Triggers verification workflow before deletion.

// Performance

System Metrics

Real-time performance metrics from our global infrastructure.

12.3ms
Avg Response Time
99.97%
System Uptime
12K/s
Requests Per Second
3.1PB
Total Storage