High-performance local data workspace

Big data
Less waiting
More living

High-performance viewing and editing for large CSV files, quantitative research and AI training data. A native Rust engine does the heavy local work—so you can finish the task and get back to your day.

Free Preview · up to 100 records · signed in-app updates · Install guide →

THE LARGE-DATA WORKSPACEInspect / Query / Edit
RRowCoveLocal workspaceMock data
▤ market_sample.parquet+
⌕ Find loaded rowsFilters 2QualityChartSave copy
Synthetic mock market records; not private data or a performance benchmark
#symboltimestampclosevolume
1DEMO-A00:00:00101.25320
2DEMO-B00:00:00202.50640
3DEMO-C00:00:00303.75480
4DEMO-A00:01:00101.50350
5DEMO-B00:01:00202.75610
6DEMO-C00:01:00304.00500
● Local processingBounded pages · original read-only
CSV · JSONL · Parquet · Arrow · SQLite · DuckDBReader capabilities →
Native Rust engineLocal parsing, indexing and queries
Bounded data browsingProjected fields and paged results
Source-preserving editsReview changes; save a separate copy
Less manual data plumbingVisible tools and authorized MCP

For people working at data scale

Your dataset is large.
Your next step should be clear.

Training data, market history or a multi-gigabyte export: see the records that answer the question, with their source context intact.

AI training & data engineering

Understand the records
before the training run.

Pretraining shards, nested conversations and preference pairs. Inspect JSONL, Parquet and Arrow without turning the entire corpus into a desktop table.

AI training data workflows

Quantitative research

Find the evidence
behind the result.

Large market-data exports, trade histories and parameter sweeps. Narrow symbols and time ranges, read exact values and trace findings to source records.

Market data & backtest workflows

Large-file analysis

Get past the file size.
Get on with the work.

GB-scale CSV, JSONL and columnar files. Start with a useful page, query supported sources and save reviewed edits as a separate copy.

Large-file viewing & editing

Performance that serves the workflow

Read the useful slice.
Keep moving.

Native Rust handles decoding, indexing, querying and persistence. Supported column projection and partition pruning reduce the data read; virtualized tables keep the desktop view focused on visible records.

Open a bounded first page, narrow the query, inspect the exact value and move on. Large scans keep progress and cancellation visible.

How the performance model works
01Choose a sourceFile, shard folder or database table
02Scope the work in RustSelect fields → prune → query → page
03Inspect and actExact values, provenance, reviewed copies

Measured with synthetic (mock) data

Big CSV files.
Less waiting.

In our 15 GB mock CSV test, RowCove Pro made the full file available in 2.94 s and completed a full-file filter in 0.32 s.

Compare desktop data tools →

Purpose-built data workflows

CSV, quant, AI
A shorter path to the answer

Choose a synthetic example to explore the workflow. The illustration shows field selection—not measured speed or guaranteed byte savings.

Mock data only

Inspect the complete value, narrow the source query, save a reviewed copy.

Project only useful fields
Source fields
24
Requested fields
4

Synthetic field counts. Not a performance benchmark.

Synthetic result previewCSV workflow guide →
Generated mock records; not customer or research data
record_idcategoryamountstatus
mock_001Demo A125.00review
mock_002Demo B98.50ready
mock_003Demo A210.25review

CSV synthetic example selected

One workspace, many formats

Work with the data
you already produce

Text exports, training records, columnar shards and local databases—with the reader and available operations made explicit.

Text & records
CSV · TSV · DSV · TXT · LOG · JSON · JSONL · NDJSONInspect tables and nested records; use supported query and copy workflows.
Columnar & spreadsheets
Parquet · Arrow IPC · Feather · XLSX · XLSTyped fields and bounded pages; capabilities depend on the reader.
Collections & databases
JSONL / Parquet / Arrow shards · SQLite · DuckDBChoose partitions, projected fields or an explicit read-only database table.
Compressed & specialist
GZIP · Zstandard · BZIP2 · ZIP · TAR · NPY / NPZ · Zarr · Safetensors · TFRecordCompressed preparation, archive catalogs or scientific metadata/framing inspection as supported. These do not all decode samples or allow edits.
Full format and operation guide →

Local data, under your control

Your dataset stays
on your machine

Parsing, indexing, queries and supported edits run locally in the Rust data engine. Dataset upload is not required to inspect your files.

Account activation and updates use network services. MCP sends the requested results to the AI client you choose; a cloud-backed client may pass them to its model provider.

Understand the privacy boundary →
Local data-processing path
  1. Your source filesOn this device
  2. Native Rust engineParse · index · query
  3. Your desktop resultsInspect · review · save a copy

MCP sharing is a separate, explicit connection.

The point of faster data work

Finish the data task
Keep the rest of your day

Fewer temporary scripts. Less manual file splitting. Less staring at a frozen table.

Spend your attention on the finding—and leave room for dinner with family, a walk outside or a game with friends.

Find the workflow that saves you steps →
A bounded assistant request
Inspect the training-data schema.
Choose one split and partition.
Return only the required fields.
Include source-file provenance.
Do not edit or export yet.
Tool responses go to the AI client you connect.

AI-assisted data work

Let the assistant ask.
Let Rust do the data work.

Use authorized local MCP tools for discovery, schema inspection and supported data queries. Review schemas, test calls and wire logs in the desktop client.

Set up a bounded MCP workflow

A tool that earns back your time

Inspect with Preview.
Go deeper with Pro.

Test a bounded first page on your own file. Pro adds supported full-file queries, quality checks, editing, export and local MCP workflows.

Preview

Get to know your data.

$0 / forever

No account. No card. Start with your own file.

Get Preview
  • Supported source discovery and schema
  • Read-only first page, up to 100 records
  • Inspect nested values and field types
  • Your original file stays untouched

Scale, privacy and capability

Know the workflow
before the wait.

Plan a TB-scale dataset
What is RowCove?

RowCove is a local data workspace for inspecting, querying and safely editing data files on your computer. Its native Rust data engine handles local parsing, indexing, querying and persistence for large-file workflows.

Does RowCove upload my files?

The desktop data engine processes files locally. Account services receive your email and purchase status, not your datasets. If you connect an AI client through MCP, the tool results you request are shared with that client and may reach its model provider.

What does Preview include?

Preview is free and does not need an account. Inspect supported file information, schema and up to 100 records in a read-only first page. Pro adds full-file workflows and MCP; available operations depend on the reader.

How much does Pro cost?

Pro costs US$15 per month or US$150 per year. The yearly plan is billed upfront and saves US$30 compared with twelve monthly payments. Applicable taxes and the final total are shown at checkout.

Can I cancel my subscription?

Yes. Open Account and choose Manage subscription. Cancel renewal in the Paddle portal. Access continues through your paid period; approved full refunds revoke the refunded purchase.

How does offline access work?

Activate Pro online and reconnect periodically to keep access current. An active subscription is required.

Which platforms are available?

Windows is the currently validated desktop platform. macOS release acceptance is still pending. Check the release page for published builds.

Is every listed format fully editable?

No. Reader capabilities differ. CSV, JSONL, Parquet and Arrow have table workflows; database sources have explicit table selection. Some scientific and training formats currently expose metadata or archive members rather than decoded samples. See the format guide.

Who is RowCove designed for?

AI data engineers working with pretraining and post-training corpora, quantitative researchers with large market or backtest data, and people inspecting or editing GB-scale CSV, JSONL and columnar files.

Can I use RowCove for TB-scale datasets?

TB-scale datasets are a target use case for scoped access through supported shards, partitions and projected fields. A TB-scale throughput and memory benchmark has not been established. Test a representative subset and plan scan, decompression and scratch-disk costs first.

Why use a native Rust data engine?

Rust handles parsing, indexing, querying and persistence locally. Supported projection and partition pruning reduce unnecessary reads, while bounded results and virtualized views keep the desktop interface focused on the records you need.

Can I use an AI assistant with RowCove through MCP?

Yes. Pro provides authorized local MCP tools for supported discovery, schema and data workflows. Review tool schemas, test calls and logs in the desktop client. Requested results go to the connected AI client and may reach its model provider.

Do website charts or screenshots contain customer data?

No. All product screenshots, examples and benchmark inputs use generated synthetic (mock) data. Comparison timings are measurements on mock inputs.

Built for the file you have been putting off

Get the answer
Get your time back

Start with a bounded first page on your own machine.

Windows Preview available. macOS release acceptance pending.

Get Windows Preview