DEV Community: James

GLM-5.2 Just Shipped a Usable 1M-Token Context Window — And It's Cheaper Than Claude

James — Sat, 20 Jun 2026 16:42:48 +0000

If you've ever hit a context wall mid-refactor — the model starts "forgetting" the file you opened twenty messages ago, or you find yourself manually re-pasting earlier code just to keep an agent loop on track — you already understand the actual problem GLM-5.2 was built to solve.

10% Discount on GLM Coding Plan: Click Here

On June 13, 2026, Z.ai (the international arm of Zhipu AI, the Tsinghua University spinout that's been building LLMs since 2019) quietly shipped GLM-5.2. No keynote. No benchmark deck at launch. Just a model card, an API endpoint, and — buried in the documentation — a context window five times larger than its predecessor's.

I've spent the past week running it against real coding tasks, reading through the architecture notes, and comparing third-party benchmark data as it's come in. Here's the full technical breakdown, plus an honest answer to "should I actually switch."
And since I use it daily myself: if you want to try it, this link gets you 10% off any GLM Coding Plan tier. Full disclosure up front — that's an affiliate link, more on the economics of that at the bottom. Everything else in this post is just the model.

TL;DR for the skim-readers

753B parameter MoE model, MIT-licensed, open weights on Hugging Face
1,000,000 token context window (glm-5.2[1m]), and it's actually stable at that length, not just nominally accepting it
Beats GPT-5.5 on SWE-bench Pro (62.1 vs 58.6) and several other long-horizon coding benchmarks
Drop-in compatible with Claude Code, Cline, OpenCode, Roo Code, Goose via an Anthropic-compatible endpoint — three env vars and you're running
API pricing: $1.40/M input tokens, $4.40/M output tokens — meaningfully cheaper than Claude Opus
GLM Coding Plan (subscription): Pro tier ~$18/month for ~2,000 prompts/week, undercutting Claude Pro

Who's actually behind this
Z.ai isn't a startup that appeared out of nowhere chasing the LLM hype cycle. It's the consumer/international brand for Zhipu AI, which has been training large language models since before "ChatGPT moment" was a phrase anyone used. The GLM (General Language Model) series has quietly tracked the frontier for years without much Western mindshare.
GLM-5 launched in February 2026 at 744B MoE parameters and was the first entry in the family to genuinely compete at the top of independent leaderboards — SWE-bench Verified scores around 77.8% put it in the same conversation as the big closed labs. GLM-5.1 followed with the GLM Coding Plan subscription model. GLM-5.2 is the biggest single-version jump the family has had, and the context window is the headline reason why.

The 1M context window — and why "1M" usually lies to you
Every lab claims big context numbers now. The catch is that most "1M token" models degrade hard somewhere past 100-200K — attention gets diffuse, instructions from early in the context get ignored, and the model effectively becomes a worse 100K model with extra latency tacked on.
Z.ai's specific claim with GLM-5.2 is that the 1M window is solid — stable performance sustained across the full length, not just technically accepted. The third-party testing that's come in since launch backs this up reasonably well.
What that buys you in practice:
Typical mid-size production repo: 300-500K tokens
→ Fits entirely in GLM-5.2's context, with room to spare

Full requirements doc + architecture decisions +
implementation + test suite, held simultaneously:
→ No more re-explaining context every 20 messages

Long agentic loops (write → test → read failure →
fix → retest → repeat):
→ 131,072 max output tokens means the loop can run
far longer before you hit a wall
If you've been manually trimming context to keep Claude Opus or GPT-5.5 within their windows, this is the actual upgrade — not a benchmark number, a workflow change.

Architecture: what's actually new
GLM-5.2 isn't a new architecture family, it's a substantial iteration on GLM-5. Two changes matter most.
IndexShare — making 1M context computationally viable
The reason most labs don't ship genuinely-usable million-token windows is cost: standard attention recalculates indices across the full context for every generated token. At 200K that's expensive but workable. At 1M it gets prohibitive fast.
GLM-5.2's fix is IndexShare — the indexer is reused across every four sparse attention layers instead of being recalculated per-layer. The result is a 2.9× reduction in per-token FLOPs at the full 1M context length. This is the unglamorous engineering work that makes long-context actually deployable instead of a marketing checkbox.
Multi-Token Prediction upgrade
GLM-5.2 also improves its MTP layer for speculative decoding, with up to 20% improvement in accepted token length during inference. Translation: faster generation, lower latency, more throughput per dollar — which compounds heavily if you're running agent loops with hundreds of chained tool calls.
Two thinking modes: High and Max
Unlike GLM-5.1's single reasoning mode, GLM-5.2 exposes High and Max effort levels. High is the default — good balance of quality, latency, and cost for routine coding tasks. Max pushes for peak reasoning quality on genuinely hard problems, at higher latency and compute cost. You select per-request, so you're not stuck paying Max-tier compute for boilerplate.
There's also GLM-5-Turbo for latency-sensitive simple tasks — think of it as occupying the same niche as Claude Haiku relative to Opus.

Benchmarks: the numbers that exist so far
Z.ai didn't publish scores at launch (same pattern as GLM-5.1), but independent evaluations have been landing over the past week. Per VentureBeat's third-party benchmark aggregation:
BenchmarkGLM-5.2GPT-5.5Claude Opus 4.8SWE-bench Pro62.158.6—FrontierSWE (Dominance)74.4%72.6%75.1%MCP-Atlas (tool use)77.075.377.8Humanity's Last Exam (w/ tools)54.752.257.9PostTrainBench34.3%25.0%—
GLM-5.2 also took first place on Design Arena (crowdsourced design benchmark), beating Claude Fable 5 with an ELO of 1360.
On the Artificial Analysis Intelligence Index, it currently leads all open-weights models at 1524 — essentially tied with GPT-5.5 (1514), ahead of MiniMax-M3 (1418) and DeepSeek V4 Pro Max (1328). Across broader model-ranking datasets it sits #7 of 380 models tracked overall, #13 of 317 for coding, #5 of 292 for agentic tasks — with a context window larger than 97% of models in that dataset.
The pattern: it's tracking at-or-near GPT-5.5 across general benchmarks, and pulling ahead specifically on long-horizon coding and sustained agentic work — exactly the use case its architecture was built for.
(Caveat, because it matters: this is independent third-party data assembled in the days after launch, not Z.ai's own published eval suite. Worth a gut-check against your own workload before fully committing production traffic.)

Setting it up with Claude Code (or Cline, or whatever you use)
This is the part that actually matters for a dev audience: GLM-5.2 runs behind an Anthropic-compatible endpoint, so if your tooling already speaks to the Anthropic API, switching is three environment variables.
bashexport ANTHROPIC_BASE_URL=https://api.z.ai/api/anthropic
export ANTHROPIC_API_KEY=your_zai_api_key
export ANTHROPIC_MODEL=glm-5.2
Or make it persistent by editing ~/.claude/settings.json:
json{
"env": {
"ANTHROPIC_BASE_URL": "https://api.z.ai/api/anthropic",
"ANTHROPIC_API_KEY": "your_zai_api_key",
"ANTHROPIC_DEFAULT_OPUS_MODEL": "glm-5.2",
"ANTHROPIC_DEFAULT_SONNET_MODEL": "glm-5-turbo",
"ANTHROPIC_DEFAULT_HAIKU_MODEL": "glm-4.5-air"
}
}
That mapping means Claude Code's tier-routing logic (Opus for hard stuff, Haiku for cheap/fast stuff) just transparently maps onto GLM's model tiers without you touching your workflow.
Officially supported tools beyond Claude Code: Cline, OpenCode, Kilo Code, Roo Code, Goose, Crush, and OpenClaw/Clawdbot.
For Cline specifically: set the API provider to "Anthropic," point the base URL at https://api.z.ai/api/anthropic, paste your Z.ai key. Done.
Two gotchas worth knowing before you flip the switch
Timeout configuration. At full 1M context, first-token latency runs longer than Claude's default timeout threshold expects. Bump it:
bashexport API_TIMEOUT_MS=120000
Otherwise you'll get spurious timeout failures on your longest-context requests — not a model problem, just a config mismatch.
Tool-result formatting in long agentic loops. If you see the model repeating a tool call instead of acknowledging the result (this shows up occasionally in extended loops), switch that specific workflow to the OpenAI-compatible endpoint instead: /api/coding/paas/v4. It's a known formatting quirk on the Anthropic-compatible shim, not on the model itself.

Pricing — this is genuinely where it gets disruptive
GLM Coding Plan (subscription)
GLM-5.2 ships included at no extra cost on every existing tier:

Lite — ~$18/mo, ~400 prompts/week. Fine for light/occasional use.
Pro — ~$18–19/mo, ~2,000 prompts/week. The realistic default for a working developer.
Max — ~$80/mo, ~8,000 prompts/week. Built for sustained all-day agentic workloads.
Team — seat-based.

(Prices fluctuate by region and promo — check current numbers on z.ai before committing.)
One thing to actually plan around: GLM-5.2 and GLM-5-Turbo run at 1× quota during off-peak hours through end of September — but 3× quota during peak hours (14:00–18:00 UTC+8). If you're running heavy batch/agentic jobs, scheduling them off-peak meaningfully stretches your plan.
Pay-as-you-go API
For building products/agents rather than using a coding assistant directly:
Input: $1.40 / million tokens
Cached input: $0.26 / million tokens
Output: $4.40 / million tokens
For comparison, Claude Opus 4.8 output tokens run roughly 5–8× higher per-token. If you're running token-heavy agentic pipelines in production, that delta compounds fast on your monthly bill.
The discount
If you're going to try the Coding Plan: this link gets you 10% off any tier. Given Pro already undercuts Claude Pro ($17–20/mo) while sitting close to GitHub Copilot Pro ($10/mo) on price, the extra 10% off makes the entry cost pretty trivial relative to what you're getting.

Open weights: the part that matters most for self-hosters
GLM-5.2 ships under a full MIT license. Not "open for research," not "free under 100K MAU," not a custom commercial-restricted license — MIT. Download it, fine-tune it, run it on your own hardware, ship it in a commercial product, no usage fees and no API dependency.
huggingface.co/zai-org/GLM-5.2
For teams in regulated industries, air-gapped environments, or anywhere data sovereignty makes "just call the OpenAI API" a non-starter, this is the actual headline. A 753B MoE model performing near GPT-5.5 level that you can fully own and host is a different category of decision than picking between API vendors.
Practical note: it's a 753B parameter MoE, so self-hosting at full precision needs serious hardware. MoE architecture means only a subset of parameters activate per token (much cheaper inference than a dense model this size), but you're still not running this on a single consumer GPU — plan your infra accordingly if you're going the self-hosted route.

Who this is actually for
You're hitting context limits regularly. If you're constantly re-summarizing earlier conversation to keep an agent on track, this solves your real bottleneck, not a benchmark vanity metric.
You're cost-sensitive on token-heavy workloads. The API pricing delta vs. Opus is large enough to matter at any real production volume.
You want to actually own your model. MIT license + self-hostable is a meaningfully different proposition than "subscribe to another API."
You're already on Claude Code or Cline. The Anthropic-compatible endpoint means near-zero switching friction — you're not relearning a tool, just pointing it somewhere else.
Who should hold off
You need Z.ai's own published benchmark suite before shipping to prod. It wasn't out at launch; independent data is still accumulating.
Your workflow is heavily multimodal. Vision support trails Claude Opus 4.8 — fine for code, weaker for image-heavy tasks.
You have no actual context or cost problem right now. If Claude Code is working fine for you today, the switching cost (re-tuning prompts, re-running evals) may not be worth it for marginal gains.

Quick-start checklist

Subscribe via for 10% off — pick Pro if unsure
Generate an API key from your Z.ai dashboard
Set your env vars (snippet above) or edit ~/.claude/settings.json
Use glm-5.2[1m] explicitly when you actually need the full context window — it's a separate model identifier
Bump API_TIMEOUT_MS for long-context requests
Schedule heavy batch work off-peak to stay inside 1× quota multiplier

Where this leaves the broader landscape
The real story here isn't really "is GLM-5.2 better than GPT-5.5" — on most benchmarks they're close enough that it depends on your specific workload. The real story is that an MIT-licensed, genuinely frontier-competitive model now exists, and that puts a ceiling on how aggressively closed labs can price their coding-plan tiers. Expect movement from the major labs on pricing/limits within the next couple of months — this kind of release tends to force it.
The Anthropic-compatible endpoint is the smart part of the GTM. Z.ai isn't asking anyone to abandon Claude Code or rebuild their tooling — it's slotting in as a cheaper/longer-context option inside the workflow you already have. That's a much easier sell than "migrate your entire stack."

Has anyone here run GLM-5.2 head-to-head against Claude Opus or GPT-5.5 on a real production repo yet? Curious whether the 1M context holds up as well as the early numbers suggest once you throw a genuinely messy legacy codebase at it — drop your results in the comments.

Article Sponsored by: Graham Miranda and Graham Miranda Network

Disclosure: the subscription link above is an affiliate link — I get a small commission if you sign up through it, at no extra cost to you (it's a 10% discount on top, not instead of). Everything else in this post reflects my own testing and reading of the publicly available benchmark data as of June 2026. Pricing and benchmark numbers are subject to change — check current figures on z.ai before making a purchasing decision.

Minimum Viable DSGVO Compliance for Startups

James — Wed, 13 May 2026 23:05:43 +0000

The 5-Minute DSGVO Compliance Checklist for Web Projects

DSGVO compliance isn't a legal essay. It's a set of technical and procedural decisions. Here's the checklist we use before any project launch.

Data Collection

[ ] List all data you collect (name, email, IP, cookies, analytics)
[ ] For each: why do you need it? (purpose limitation)
[ ] For each: how long do you keep it? (storage limitation)
[ ] Can you delete it on user request? (right to erasure)

Technical Measures

[ ] HTTPS everywhere (TLS 1.3)
[ ] No third-party trackers (Google Analytics, Facebook Pixel) without consent
[ ] Cookie banner for non-essential cookies (strict opt-in)
[ ] Server location in EU (or SCCs for non-EU)
[ ] Access logs stripped of PII or rotated after 30 days
[ ] Database encryption at rest

Documentation

[ ] Privacy policy (German + English, plain language)
[ ] Data processing agreement (if using third-party services)
[ ] Incident response plan (72-hour notification requirement)
[ ] User rights procedure (how to handle access/erasure requests)

Team

[ ] Data protection officer (required for > 10 employees processing personal data)
[ ] Employee training (annual, documented)
[ ] Access controls (role-based, minimal privilege)

Quick Wins

Replace Google Analytics with Plausible (€9/month, EU-hosted, no cookies).
Replace reCAPTCHA with hCaptcha or Friendly Captcha (better privacy posture).
Host in EU (Hetzner, OVH, Scaleway — all cheaper than AWS anyway).

The Honest Truth

Most DSGVO violations aren't malicious. They're careless:

Forgetting to add a privacy policy
Logging IPs indefinitely
Using US-hosted analytics without SCCs
Not documenting data flows

This checklist fixes the careless mistakes. The hard stuff (legitimate interest assessments, DPIAs) comes later — but only after the basics are solid.

Graham Miranda is the founder of Graham Miranda UG (Berlin, HRB 36794), building DSGVO-compliant automation and privacy tools.

Launching in Germany? Run This Checklist First

James — Wed, 13 May 2026 23:04:38 +0000

The 5-Minute DSGVO Compliance Checklist for Web Projects

DSGVO compliance isn't a legal essay. It's a set of technical and procedural decisions. Here's the checklist we use before any project launch.

Data Collection

[ ] List all data you collect (name, email, IP, cookies, analytics)
[ ] For each: why do you need it? (purpose limitation)
[ ] For each: how long do you keep it? (storage limitation)
[ ] Can you delete it on user request? (right to erasure)

Technical Measures

[ ] HTTPS everywhere (TLS 1.3)
[ ] No third-party trackers (Google Analytics, Facebook Pixel) without consent
[ ] Cookie banner for non-essential cookies (strict opt-in)
[ ] Server location in EU (or SCCs for non-EU)
[ ] Access logs stripped of PII or rotated after 30 days
[ ] Database encryption at rest

Documentation

[ ] Privacy policy (German + English, plain language)
[ ] Data processing agreement (if using third-party services)
[ ] Incident response plan (72-hour notification requirement)
[ ] User rights procedure (how to handle access/erasure requests)

Team

[ ] Data protection officer (required for > 10 employees processing personal data)
[ ] Employee training (annual, documented)
[ ] Access controls (role-based, minimal privilege)

Quick Wins

The Honest Truth

Most DSGVO violations aren't malicious. They're careless:

Forgetting to add a privacy policy
Logging IPs indefinitely
Using US-hosted analytics without SCCs
Not documenting data flows

This checklist fixes the careless mistakes. The hard stuff (legitimate interest assessments, DPIAs) comes later — but only after the basics are solid.

Graham Miranda is the founder of Graham Miranda UG (Berlin, HRB 36794), building DSGVO-compliant automation and privacy tools.

DSGVO Compliance in 5 Minutes: A Practical Checklist

James — Wed, 13 May 2026 23:03:32 +0000

The 5-Minute DSGVO Compliance Checklist for Web Projects

DSGVO compliance isn't a legal essay. It's a set of technical and procedural decisions. Here's the checklist we use before any project launch.

Data Collection

[ ] List all data you collect (name, email, IP, cookies, analytics)
[ ] For each: why do you need it? (purpose limitation)
[ ] For each: how long do you keep it? (storage limitation)
[ ] Can you delete it on user request? (right to erasure)

Technical Measures

[ ] HTTPS everywhere (TLS 1.3)
[ ] No third-party trackers (Google Analytics, Facebook Pixel) without consent
[ ] Cookie banner for non-essential cookies (strict opt-in)
[ ] Server location in EU (or SCCs for non-EU)
[ ] Access logs stripped of PII or rotated after 30 days
[ ] Database encryption at rest

Documentation

[ ] Privacy policy (German + English, plain language)
[ ] Data processing agreement (if using third-party services)
[ ] Incident response plan (72-hour notification requirement)
[ ] User rights procedure (how to handle access/erasure requests)

Team

[ ] Data protection officer (required for > 10 employees processing personal data)
[ ] Employee training (annual, documented)
[ ] Access controls (role-based, minimal privilege)

Quick Wins

The Honest Truth

Most DSGVO violations aren't malicious. They're careless:

Forgetting to add a privacy policy
Logging IPs indefinitely
Using US-hosted analytics without SCCs
Not documenting data flows

This checklist fixes the careless mistakes. The hard stuff (legitimate interest assessments, DPIAs) comes later — but only after the basics are solid.

Graham Miranda is the founder of Graham Miranda UG (Berlin, HRB 36794), building DSGVO-compliant automation and privacy tools.

Search Index Architecture for Privacy-First Engines

James — Wed, 13 May 2026 23:02:26 +0000

Elasticsearch vs. PostgreSQL Full-Text: Search Engine Indexing Deep Dive

Every search engine needs an index. The question is: which technology builds it?

PostgreSQL Full-Text Search

Built-in since PostgreSQL 8.3. Surprisingly capable.

Pros:

Zero additional infrastructure
ACID compliance (index stays consistent with data)
Good for < 1M documents
Supports German stemming, compound word handling
tsvector/tsquery is fast for simple needs

Cons:

No distributed search
Limited faceting and aggregation
Relevance scoring is basic
No built-in synonym support

Elasticsearch

The industry standard for search.

Pros:

Distributed by design (shards, replicas)
Advanced relevance scoring (BM25, custom functions)
Real-time indexing
Faceting, aggregation, geospatial
Plugin ecosystem (synonyms, analyzers)

Cons:

Additional infrastructure (cluster management)
Memory hungry (heap size tuning required)
Eventually consistent (not ACID)
Complex query DSL learning curve

What We Chose (and Why)

We use both:

PostgreSQL: Primary data store, user accounts, query logs (minimal), metadata
Elasticsearch: Search index only, rebuilt from PostgreSQL nightly

This hybrid gives us ACID for critical data and search performance for queries. If Elasticsearch fails, we can rebuild from PostgreSQL. If PostgreSQL is slow for search, Elasticsearch handles it.

German Language Challenges

German search is harder than English:

Compound words ("Datenschutzgrundverordnung")
Umlaut normalization (ä → ae or a?)
Case inflection
Dialect variations

Our solution: Custom Elasticsearch analyzer chain:

ICU tokenizer (handles compound words)
German stemmer (Snowball)
Umlaut normalizer (ä → a, ö → o, ü → u)
Synonym filter (DSGVO → Datenschutzgrundverordnung)

Graham Miranda builds search infrastructure at Graham Miranda UG (Berlin, HRB 36794).

Full-Text Search at Scale: Our Indexing Choice

James — Wed, 13 May 2026 23:01:21 +0000

Elasticsearch vs. PostgreSQL Full-Text: Search Engine Indexing Deep Dive

Every search engine needs an index. The question is: which technology builds it?

PostgreSQL Full-Text Search

Built-in since PostgreSQL 8.3. Surprisingly capable.

Pros:

Zero additional infrastructure
ACID compliance (index stays consistent with data)
Good for < 1M documents
Supports German stemming, compound word handling
tsvector/tsquery is fast for simple needs

Cons:

No distributed search
Limited faceting and aggregation
Relevance scoring is basic
No built-in synonym support

Elasticsearch

The industry standard for search.

Pros:

Distributed by design (shards, replicas)
Advanced relevance scoring (BM25, custom functions)
Real-time indexing
Faceting, aggregation, geospatial
Plugin ecosystem (synonyms, analyzers)

Cons:

Additional infrastructure (cluster management)
Memory hungry (heap size tuning required)
Eventually consistent (not ACID)
Complex query DSL learning curve

What We Chose (and Why)

We use both:

PostgreSQL: Primary data store, user accounts, query logs (minimal), metadata
Elasticsearch: Search index only, rebuilt from PostgreSQL nightly

This hybrid gives us ACID for critical data and search performance for queries. If Elasticsearch fails, we can rebuild from PostgreSQL. If PostgreSQL is slow for search, Elasticsearch handles it.

German Language Challenges

German search is harder than English:

Compound words ("Datenschutzgrundverordnung")
Umlaut normalization (ä → ae or a?)
Case inflection
Dialect variations

Our solution: Custom Elasticsearch analyzer chain:

ICU tokenizer (handles compound words)
German stemmer (Snowball)
Umlaut normalizer (ä → a, ö → o, ü → u)
Synonym filter (DSGVO → Datenschutzgrundverordnung)

Graham Miranda builds search infrastructure at Graham Miranda UG (Berlin, HRB 36794).

Building a Search Index: Elasticsearch vs. PostgreSQL

James — Wed, 13 May 2026 23:00:15 +0000

Elasticsearch vs. PostgreSQL Full-Text: Search Engine Indexing Deep Dive

Every search engine needs an index. The question is: which technology builds it?

PostgreSQL Full-Text Search

Built-in since PostgreSQL 8.3. Surprisingly capable.

Pros:

Zero additional infrastructure
ACID compliance (index stays consistent with data)
Good for < 1M documents
Supports German stemming, compound word handling
tsvector/tsquery is fast for simple needs

Cons:

No distributed search
Limited faceting and aggregation
Relevance scoring is basic
No built-in synonym support

Elasticsearch

The industry standard for search.

Pros:

Distributed by design (shards, replicas)
Advanced relevance scoring (BM25, custom functions)
Real-time indexing
Faceting, aggregation, geospatial
Plugin ecosystem (synonyms, analyzers)

Cons:

Additional infrastructure (cluster management)
Memory hungry (heap size tuning required)
Eventually consistent (not ACID)
Complex query DSL learning curve

What We Chose (and Why)

We use both:

PostgreSQL: Primary data store, user accounts, query logs (minimal), metadata
Elasticsearch: Search index only, rebuilt from PostgreSQL nightly

This hybrid gives us ACID for critical data and search performance for queries. If Elasticsearch fails, we can rebuild from PostgreSQL. If PostgreSQL is slow for search, Elasticsearch handles it.

German Language Challenges

German search is harder than English:

Compound words ("Datenschutzgrundverordnung")
Umlaut normalization (ä → ae or a?)
Case inflection
Dialect variations

Our solution: Custom Elasticsearch analyzer chain:

ICU tokenizer (handles compound words)
German stemmer (Snowball)
Umlaut normalizer (ä → a, ö → o, ü → u)
Synonym filter (DSGVO → Datenschutzgrundverordnung)

Graham Miranda builds search infrastructure at Graham Miranda UG (Berlin, HRB 36794).

The Berlin Tech Ecosystem: A Founder's Guide

James — Wed, 13 May 2026 22:59:10 +0000

Running a Tech Business in Berlin: Costs, Compliance, and Community

Berlin isn't the cheapest European city for startups. But it offers something rare: a combination of technical talent, regulatory clarity, and startup density that creates genuine competitive advantage.

Real Costs (2026)

Expense	Monthly Cost
Office (WeWork / similar)	€400-800/person
Developer salary (mid-level)	€4,500-6,500
Hetzner VPS (production)	€15-45
Legal/accounting (UG)	€300-500
Health insurance (public)	€350-450/person
Rent (1BR apartment)	€1,000-1,500

Total burn for 3-person team: ~€18,000-25,000/month.

Why a UG (Not GmbH)

The Unternehmergesellschaft (UG) is Germany's "mini-GmbH":

€1 minimum capital (vs. €25,000 for GmbH)
Same liability protection
Same legal standing
Must retain 25% of profits until €25,000 reached (then convert to GmbH)

For bootstrapped founders, the UG structure removes the capital barrier entirely.

Compliance Advantage

Berlin-based means:

DSGVO compliance by default (German data protection authority)
EU AI Act jurisdiction clear
German contract law (predictable, well-tested)
Tax treaties across EU and globally

For B2B clients, "Berlin-based" signals regulatory maturity that "Delaware-based" does not.

The Community

Berlin's tech scene is dense and collaborative:

Weekly meetups for every technology stack
Strong open-source culture
EU-funded research partnerships
Talent pool from TU Berlin, HU Berlin, and international graduates

The competition for talent is real. But so is the quality.

Graham Miranda is the founder of Graham Miranda UG (Berlin, HRB 36794).

Why We Incorporated in Berlin (Not Delaware)

James — Wed, 13 May 2026 22:58:04 +0000

Running a Tech Business in Berlin: Costs, Compliance, and Community

Real Costs (2026)

Expense	Monthly Cost
Office (WeWork / similar)	€400-800/person
Developer salary (mid-level)	€4,500-6,500
Hetzner VPS (production)	€15-45
Legal/accounting (UG)	€300-500
Health insurance (public)	€350-450/person
Rent (1BR apartment)	€1,000-1,500

Total burn for 3-person team: ~€18,000-25,000/month.

Why a UG (Not GmbH)

The Unternehmergesellschaft (UG) is Germany's "mini-GmbH":

€1 minimum capital (vs. €25,000 for GmbH)
Same liability protection
Same legal standing
Must retain 25% of profits until €25,000 reached (then convert to GmbH)

For bootstrapped founders, the UG structure removes the capital barrier entirely.

Compliance Advantage

Berlin-based means:

DSGVO compliance by default (German data protection authority)
EU AI Act jurisdiction clear
German contract law (predictable, well-tested)
Tax treaties across EU and globally

For B2B clients, "Berlin-based" signals regulatory maturity that "Delaware-based" does not.

The Community

Berlin's tech scene is dense and collaborative:

Weekly meetups for every technology stack
Strong open-source culture
EU-funded research partnerships
Talent pool from TU Berlin, HU Berlin, and international graduates

The competition for talent is real. But so is the quality.

Graham Miranda is the founder of Graham Miranda UG (Berlin, HRB 36794).

Berlin Startup Costs 2026: Real Numbers

James — Wed, 13 May 2026 22:56:59 +0000

Running a Tech Business in Berlin: Costs, Compliance, and Community

Real Costs (2026)

Expense	Monthly Cost
Office (WeWork / similar)	€400-800/person
Developer salary (mid-level)	€4,500-6,500
Hetzner VPS (production)	€15-45
Legal/accounting (UG)	€300-500
Health insurance (public)	€350-450/person
Rent (1BR apartment)	€1,000-1,500

Total burn for 3-person team: ~€18,000-25,000/month.

Why a UG (Not GmbH)

The Unternehmergesellschaft (UG) is Germany's "mini-GmbH":

€1 minimum capital (vs. €25,000 for GmbH)
Same liability protection
Same legal standing
Must retain 25% of profits until €25,000 reached (then convert to GmbH)

For bootstrapped founders, the UG structure removes the capital barrier entirely.

Compliance Advantage

Berlin-based means:

DSGVO compliance by default (German data protection authority)
EU AI Act jurisdiction clear
German contract law (predictable, well-tested)
Tax treaties across EU and globally

For B2B clients, "Berlin-based" signals regulatory maturity that "Delaware-based" does not.

The Community

Berlin's tech scene is dense and collaborative:

Weekly meetups for every technology stack
Strong open-source culture
EU-funded research partnerships
Talent pool from TU Berlin, HU Berlin, and international graduates

The competition for talent is real. But so is the quality.

Graham Miranda is the founder of Graham Miranda UG (Berlin, HRB 36794).

Building a Privacy Frontend with Next.js

James — Wed, 13 May 2026 22:55:53 +0000

Why We Chose Next.js Over React for Our Privacy Search Engine

Frontend frameworks seem interchangeable. For a privacy-focused product, the choice matters more than you'd think.

The Privacy Problem with SPAs

Traditional React SPAs:

Execute all logic in the browser
Make API calls directly to third parties
Expose the user's IP to every service
Require JavaScript (fingerprinting surface)

For asearchz.online, this was unacceptable. Every API call a user made would expose their IP to Bing, Brave, or other search sources.

Why Next.js (Server-Side Rendering)

With Next.js SSR:

The server makes API calls to search sources
User IP stays between user and our server only
Results are rendered server-side, sent as HTML
JavaScript is optional (works without it)

Performance Benefits

SSR is actually faster for search:

First contentful paint: 200-300ms
No hydration delay (content is already HTML)
No client-side state management complexity
CDN caching of rendered pages

Trade-offs

Next.js SSR has costs:

Server compute per request (higher than static)
Less interactive without client JS
Harder to implement real-time features

For a search engine, these trade-offs are minimal. Users want fast results, not real-time collaboration.

The Architecture

User → Cloudflare CDN → Next.js Server → FastAPI Backend → Search APIs

The user's browser never talks to Bing, Brave, or any search source. Our server does. The user's IP is known only to us — and we don't log it.

Graham Miranda builds privacy-first infrastructure at Graham Miranda UG (Berlin, HRB 36794).

Next.js vs. React: Privacy Implications

James — Wed, 13 May 2026 22:54:48 +0000

Why We Chose Next.js Over React for Our Privacy Search Engine

Frontend frameworks seem interchangeable. For a privacy-focused product, the choice matters more than you'd think.

The Privacy Problem with SPAs

Traditional React SPAs:

Execute all logic in the browser
Make API calls directly to third parties
Expose the user's IP to every service
Require JavaScript (fingerprinting surface)

For asearchz.online, this was unacceptable. Every API call a user made would expose their IP to Bing, Brave, or other search sources.

Why Next.js (Server-Side Rendering)

With Next.js SSR:

The server makes API calls to search sources
User IP stays between user and our server only
Results are rendered server-side, sent as HTML
JavaScript is optional (works without it)

Performance Benefits

SSR is actually faster for search:

First contentful paint: 200-300ms
No hydration delay (content is already HTML)
No client-side state management complexity
CDN caching of rendered pages

Trade-offs

Next.js SSR has costs:

Server compute per request (higher than static)
Less interactive without client JS
Harder to implement real-time features

For a search engine, these trade-offs are minimal. Users want fast results, not real-time collaboration.

The Architecture

User → Cloudflare CDN → Next.js Server → FastAPI Backend → Search APIs

The user's browser never talks to Bing, Brave, or any search source. Our server does. The user's IP is known only to us — and we don't log it.

Graham Miranda builds privacy-first infrastructure at Graham Miranda UG (Berlin, HRB 36794).