Report output

A long answer laid out as a report: sections with a contents list, figures and numbered sources, with a short version that opens into the full one.

Research report

Deep research

Should we move our EU customers to a Frankfurt region?

28 Oct 2026Read 41 sources9 min read

Summary

Yes, but only for customers in Germany, Austria and Switzerland, and not before Q2. Frankfurt cuts p95 latency for DACH users by about 60% and is the only way to keep the 23 accounts whose contracts require German hosting.

Moving every EU customer would cost about $2,300 more a month, make the UK slower, and buys nothing for GDPR, which treats Ireland and Germany the same.

1Where EU traffic comes from

Germany is the largest EU market at 31% of sessions, followed by the UK at 19% and France at 14%. Poland and Italy are small but growing quickly, and both sit far from Ireland on the network.

Revenue is more concentrated than traffic. The DACH region is 44% of EU annual recurring revenue, mostly from mid-sized manufacturers and two public-sector accounts.

2Latency

We served 4% of EU sessions from a Frankfurt canary for two weeks with the same build and instance types. Central and eastern Europe improved the most. Spain was flat, and the UK got about 9 ms slower.

p95 API latency, msIreland todayFrankfurt, measured

Germany

Poland

Italy

France

Netherlands

Spain

United Kingdom

0204060

Figure 1. Measured p95 by client country, 10–24 Oct. Amber marks countries that got slower.

The gain matters most on the editor, which makes six to ten sequential API calls when a document opens. At p95 that is roughly 200 ms saved for a German user before the first paint.

3Cost

Frankfurt list prices are 5–8% higher across everything we run. Our savings plan covers both regions, so the gap holds after discounts.

Monthly cost by region
Monthly, on-demand	eu-west-1	eu-central-1	Change
Compute, 42 × m7g.2xlarge	$18,420	$19,710	+7.0%
Postgres, 3 × db.r7g.4xlarge	$9,860	$10,640	+7.9%
Data transfer out	$3,150	$3,310	+5.1%
S3 and backups	$1,240	$1,330	+7.3%
Total	$32,670	$34,990	+7.1%

Table 1. Current EU footprint priced in each region, before savings plan.

During a migration we would also run both regions for six to ten weeks and pay for cross-region replication, about $4,800 one-off.

4Compliance and data residency

GDPR does not prefer one member state over another, so moving from Ireland to Germany changes nothing for most customers.

The pressure is contractual. German public-sector tenders often ask for data inside Germany and C5 attestation. Two renewals worth $410k ARR are due in May with that clause.

5Migration risk

The last region move overran by five weeks, mostly because bucket names and region strings were hard-coded in three services. Those services have since moved to config, but the export worker still has two.

Postgres logical replication covers the data, but sequences and schema changes need a freeze window.
Webhook IPs change, and 38 customers allow-list ours.
Search indexes rebuild from scratch, about 14 hours for the DACH tenants.

6Recommendation

Stand up eu-central-1 as a second EU region and move DACH tenants only, starting with the two public-sector accounts before their May renewals. Keep the UK, Ireland and Iberia in eu-west-1.

Revisit a full move in a year, once Poland and Italy are large enough for the latency gain to show up in retention.

Sources8 cited of 41 read

Loading preview…

Install

1
Run this command in your Tailwind CSS project. It adds components/ai/report-output-document.tsx and installs its dependencies.
$ npx shadcn@latest add https://gradientdeck.com/ai-components/r/report-output-document.json

Usage & API

Example

report-output-document.tsx

import { ResearchReport } from "@/components/ai/report-output-document"

<ResearchReport
  report={report}
  shareUrl="…"
  onExport={() => {}}
/>

Props `ResearchReport`

Prop	Type & description	Required
`report`	`Report`	Required
`shareUrl`	`string`Link shown in the share popover.	Required
`onExport`	`(format: ExportFormat) => Promise<void>`Resolve when the file is ready. The toolbar shows progress while it's pending.	Required
`onBack`	`() => void`	Optional
`backLabel`	`string`Text for the back button, e.g. the chat title.	Optional

Dependencies

React
Tailwind CSS
motion
lucide-react

Implementation notes

The full report is a window with a back button, the label Research report, and the question in the toolbar. Copy as Markdown flips to Copied. Export opens a menu for PDF, Word document and Markdown, then shows Preparing and a downloaded filename while the promise you passed is pending. Share opens a link field, a Copy button, and a switch for anyone at the workspace versus only you. A contents list on the left, and a sticky contents menu on a narrow screen, jumps to Summary, each numbered section and Sources. A bar under the toolbar and a minutes-left line follow the scroll. The preview is a Frankfurt-region report with a summary box, six sections, a chart, a table and eight sources.

Example

report-output-brief.tsx

import { ReportBrief } from "@/components/ai/report-output-brief"

<ReportBrief
  report={report}
  expanded={true}
  onExpandedChange={() => {}}
/>

Props `ReportBrief`

Prop	Type & description	Required
`report`	`ReportBriefData`	Required
`expanded`	`boolean`	Required
`onExpandedChange`	`(expanded: boolean) => void`	Required
`scrollRef`	`RefObject<HTMLElement \| null>`The scroll container the brief sits in. Used to keep jumps inside it.	Optional

Dependencies

React
Tailwind CSS
motion
lucide-react

Implementation notes

The brief sits in a chat reply after a line that says how long the research took and how many sources were read. A header names it Research report, with the date and a minutes-to-read figure. The headline is one sentence. Three numbered points each carry a High, Medium or Low chip and a short basis. Open full report expands section chips, the sections, a latency chart, a cost table and the source list. The sources button jumps there and opens the report if it was closed. Under the card are Copy, a good-response and a bad-response toggle, and follow-up chips that fill the composer. The surrounding preview is a chat with a searchable sidebar.

Choosing a layout

Use the document when the answer is something a person will read for several minutes, scroll, export or hand to someone who should not see the chat. Use the brief when the same material has to stay inside a thread, with a short version first and the sections one click away. Both assume you already have sections and numbered sources.

A single quoted passage beside the answer is the source viewer. A queue of agent runs is the agent inbox. If the model only returned a paragraph, neither variant earns its chrome. The contents list, the confidence marks and the export menu are for a report that already has a shape.

What does Export actually download?

The menu offers PDF, a Word document and Markdown, and the toolbar shows progress until the onExport promise resolves. The component does not build the file. Copy as Markdown does write text, from the report already on the page, and puts it on the clipboard.

Do the confidence chips mean the model scored the point?

They show the confidence and the basis you put on each point of the brief. The document variant has no confidence chips. It has a summary, sections and numbered citations instead.

Message3 variants

A single chat message from the person or the assistant, in three layouts.

Message actions

The row under an assistant reply: copy, regenerate, thumbs up or down with a short feedback form, and share.

Branch picker

Steps between alternative versions of a reply, like 2 / 3, with a crossfade.

Report output

Should we move our EU customers to a Frankfurt region?

Summary

1Where EU traffic comes from

2Latency

3Cost

4Compliance and data residency

5Migration risk

6Recommendation

Sources8 cited of 41 read

Install

Usage & API

Example

Props ResearchReport

Dependencies

Example

Props ReportBrief

Dependencies

More in Messages

Should we move our EU customers to a Frankfurt region?

Summary

1Where EU traffic comes from

2Latency

3Cost

4Compliance and data residency

5Migration risk

6Recommendation

Sources8 cited of 41 read

Props `ResearchReport`

Props `ReportBrief`