Website preview. Not yet public. Bracketed placeholders are filled in before launch.

A PRIVATE WORKSPACE FOR APP DEVELOPERS

Your reports. Your AI.
Your next release.

Bring encrypted feedback and crash reports to the Mac.
Keep your symbols local. Work with the coding agent you choose.

One place for what came in and what comes next.Fictional sample data
Encrypted reports. Your keys.Your own AI. Your choice.Local symbols. Your Mac.

LESS SORTING. MORE SHIPPING.

A report is the beginning.
The fix is the point.

Keep the evidence and the work together, from the first crash to the build that puts it right.

YOUR REPORTS. YOUR KEYS.

The service stores it.
Your Mac opens it.

Report contents and attachments are encrypted before they leave the device. Your private keys stay on your Macs, so the collector can deliver the reports without reading what they say.

The service still handles operational metadata, such as report type and size.

▯Your appSeals the report
▤The collectorStores encrypted content
▱Your MacHolds the keys

THE CONTEXT YOUR AGENT WAS MISSING

Your code is already there.
Bring the report, too.

Give your chosen coding agent the evidence behind the bug, alongside your source, tests, and project instructions.

FLIGHTDATAKIT

Collect the useful details.

A native SwiftUI feedback form can include custom questions, screenshots, and the document that went wrong. People can preview files before sending.

Button("Send Feedback…") {
    showsFeedback = true
}
.feedbackSheet(
    isPresented: $showsFeedback
)
SwiftUI view excerpt · Requires a configured FlightDataContainer
BRING YOUR OWN AI · LOCAL MCP

Use the agent you know.

Connect your preferred MCP-capable coding agent. Let it inspect reports and work items with permissions controlled by the Mac app.

Your model may run locally or with a cloud provider; you choose. Provider charges are separate.

FITS THE TOOLS YOU ALREADY USE

At home with Xcode.
Alongside TestFlight.

AUTOMATIC LOCAL dSYM COLLECTION

Your symbols, already here.

Choose your Xcode Archives folder once. Flight Data Recorder watches for new builds while it runs and keeps local copies of your apps’ dSYMs.

Copies remain even if you remove the original archive.

FROM BETA TO RELEASE

The feedback loop stays open.

Use the same feedback form in your TestFlight and released builds. Keep reports, requested features, and the work they lead to in one Mac workspace.

✧TestFlightBeta feedback
✓Released appCustomer feedback
f
One product. One timeline.Original reports stay with the work.

Reports sent through FlightDataKit. TestFlight feedback import is planned, not available yet.

SMALL-TEAM PRICING

A useful part of your toolkit.
A small part of your budget.

Choose your hosted capacity. Keep the core workflow.

Free

$0while you test

Try the complete workflow.

  • 1 app
  • 50 reports a month
  • 25 MB of storage
  • Reports kept 30 days

Studio

$9.99/ month

More room as your apps grow.

  • 25 apps
  • 25,000 reports a month
  • 20 GB of storage
  • Reports kept while you subscribe

Every plan includes encrypted reports, MCP access, and local dSYM collection.

Prices in US dollars. Every report counts, from TestFlight and debug builds as well as the App Store. Flight Data Recorder is a new service, and we’re still learning what people need. If these limits don’t fit how you work, email us. Every limit is on the support page. Your AI provider’s charges are separate.

A FEW USEFUL DETAILS

What stays where.

Does everything stay on my Mac?

Your dSYMs and private keys stay on your Macs. Report content is encrypted before upload and stored by the service; operational metadata remains visible to it. An approved cloud-backed agent may send the readable content it accesses to its model provider.

Are crash reports automatically symbolicated?

Flight Data Recorder collects your dSYMs automatically into a local library indexed by UUID. Automatic symbolication of incoming crash reports isn’t available yet. Archives built elsewhere can be imported manually.

How does it work with TestFlight?

Include FlightDataKit in your beta and released builds to send feedback through the same form. Flight Data Recorder works alongside TestFlight; it does not currently import feedback collected by Apple.

Do I need another AI subscription?

Flight Data Recorder connects to the MCP-capable coding agent you choose. Use your existing provider plan or a suitable local model. There’s no AI add-on to buy; your provider’s own terms and charges still apply.

Your next release.
With the whole story.

Encrypted reports. Your AI. Your Mac.

Take another look