BigQuery loads from Google Cloud Storage and exports back to it. Files.com is the governed front door on the GCS bucket: it collects partner files over the protocols partners actually use, reshapes them, lands them where the load reads, and delivers exports back out.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
BigQuery’s loading model is clean: put files in Google Cloud Storage, and load jobs, scheduled transfers, and external tables read them from there. The mess lives upstream — counterparties on SFTP, feeds arriving PGP-encrypted, formats the load won’t accept, and the gsutil scripts and Cloud Functions somebody wrote to hold it all together.
Files.com owns everything between the sender and the bucket. Partners deliver over their own scoped credentials, TransformScript reshapes what needs reshaping, the GCS connection lands files where BigQuery loads, and Pub/Sub events tell the rest of your Google stack the moment data is ready.
Partner and vendor feeds land the same way whichever storage the warehouse reads: a drop point per sender, and every file in your own bucket the moment it arrives.
Intake to the bucket, events to the pipeline, and exports delivered outward. Each runs on Files.com in production.
GCS is BigQuery’s loading dock. Files.com connects to your GCS bucket and an Automation writes each inbound partner file into it the moment it arrives, so the load job or scheduled transfer finds the data already in place.
Mount the GCS bucket and its folders appear as Files.com folders: a partner upload lands directly in GCS, and a BigQuery export dropped in the bucket is immediately reachable over every Files.com protocol and share surface.
Files.com publishes file events to Google Pub/Sub, so an arriving feed triggers the Dataflow job or BigQuery load the moment the file lands. Analytics stay current instead of waiting on a timer.
BigQuery loads CSV, JSON, Avro, Parquet, and ORC — not whatever a counterparty happened to send. TransformScript converts formats in the flow, and Automations split and rename, so what reaches the bucket is what the load accepts.
BigQuery exports land in GCS; Automations pick them up, encrypt under a recipient’s PGP key where mandated, and deliver over SFTP or whatever protocol each counterparty runs, with every delivery logged.
A scheduled load over a bucket nobody fed succeeds at loading nothing. Delivery monitoring knows when each upstream feed is due and raises an alert when the window closes without a file, before the dashboard shows yesterday’s numbers as today’s.
How Files.com attaches to the bucket, and why nothing on the BigQuery side changes.
Files.com connects to Google Cloud Storage with a service account key (JSON), HMAC keys over Google’s S3-compatible XML API, or OAuth. One connection covers mounts, syncs, and automation targets against the bucket.
A Remote Server Mount presents the bucket as live Files.com folders with nothing copied; a scheduled Sync pushes or pulls in batches. Inbound partner data and outbound BigQuery exports each get whichever shape fits.
BigQuery load jobs, scheduled Data Transfer Service runs, and external tables all read the bucket exactly as they do today. Files.com feeds and drains the bucket; nothing about the BigQuery side changes.
Each partner or system delivering data gets its own scoped credential and folder, so no sender ever sees another’s files, and the audit log records every arrival, transformation, and write to the bucket.
The migration had to add vendor isolation, tighter payroll access, and auditability while leaving existing SFTP paths and automations intact.
Read The Story
A branded portal, scripted provisioning, and automated validation gave the finance team control of auditable vendor intake at scale.
Read The Story
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
What data teams ask most when wiring partner file intake to BigQuery.
No. BigQuery loads from Google Cloud Storage, not from SFTP servers. Files.com bridges the two: counterparties deliver over SFTP, FTPS, AS2, or a browser, and Files.com writes the files into the GCS bucket your load jobs and scheduled transfers already read.
Files.com connects to Google Cloud Storage through the GCS integration, authenticated by a service account key, HMAC keys, or OAuth. Connect the bucket as a Remote Server Mount that writes directly into it, or as a scheduled Sync that moves batches. Automations route each inbound file to the right bucket path the moment it arrives.
Yes. Files.com publishes file events to Google Pub/Sub, so an upload can trigger a Cloud Run service, a Dataflow job, or a BigQuery load immediately. No Cloud Function watching a bucket, and no timer-based load running against data that isn’t there yet.
BigQuery accepts CSV, newline-delimited JSON, Avro, Parquet, and ORC. TransformScript converts CSV, XML, and JSON in the flow, so a counterparty’s format problem gets fixed before the file reaches the bucket, not in the load job’s error log.
Yes. BigQuery exports to GCS, and Files.com takes it from there: Automations rename to each recipient’s convention, encrypt per recipient where PGP is mandated, and deliver over the protocol each counterparty runs, with every delivery on the record.
No. A mounted bucket means the bytes stay in GCS, in your project and region. Files.com is the protocol and governance surface over the bucket; partner uploads land in it directly, and your residency posture holds.
Partners deliver to Files.com however they can: SFTP, FTPS, AS2, the S3-compatible API, a browser upload, or an email inbox that turns attachments into files. Each sender gets a scoped credential and folder, with PGP decryption on arrival where feeds come encrypted.
Delivery monitoring in Files.com defines when each feed is due and alerts when the window closes without a file. You get a same-hour alert instead of a stale dashboard discovered in a Monday meeting.
Yes. Files.com runs SOC 2 Type II, encrypts in transit and at rest, and logs every access and every write to the bucket. A pre-approved HIPAA business associate agreement comes with Files.com Enterprise, and retention policies clear delivered files on your schedule.
Files.com replaces the glue between senders and the bucket: gsutil scripts, Cloud Functions watching folders, the hand-carried uploads from partners who can’t speak GCS, and the monitoring nobody built. One governed platform receives, reshapes, and lands the data where BigQuery already loads.
Receive, transform, and land every file your warehouse loads, with events firing the moment data is ready.
No credit card required • Free for 7 days • Live in minutes