Now in private beta
We run your research data feeds inside your AWS account
For funds and family offices without a data engineering team. We check every vendor file before your analysts see it and stop the bad ones. By a time you set each morning, you get a short report on every feed.
See our privacy notice.
- Your AWS account
- Everything runs there, on your bill
- Apache Iceberg on S3
- Open tables you can read without our code
- Snowflake, Athena, DuckDB
- Read the tables in place. Postgres gets a copy.
- Point-in-time
- Every row records when the source published it
What happens when a vendor sends bad data
Your vendor renames a column at 2 a.m. The file fails its checks, so nothing from it reaches your tables. Your analysts keep working on yesterday's data, and you get a message saying what broke. We call this a hold.
A vendor changes a file's format without telling you
The file is held while we update the feed's rules.
A vendor delivers late
Your models still build by your deadline, with that feed's last good data. The report marks it stale.
A source restates old numbers
The revision is a new row. Backtests only see it from when it was published.
A ticker changes hands
If two feeds disagree about which company it is, your models are held.
How it works
Set up in your account
Our Terraform builds it in your AWS account, from a repo in your GitHub.
Every file checked
We fetch each feed and check it against its rules.
The morning report
One message to Slack or email at the time you set. A held feed's line says what broke and links the fix.
Security
Your data stays in your AWS account
Metadata only
Only run metadata leaves your account. No data values, no raw error text.
Three access roles
None can read your secrets or change your infrastructure. One edit revokes any of them.
Changes in your GitHub
Every change is a pull request in a repo you own.
Yours if you leave
Your setup keeps running. Only upgrades and our operations stop.
Common questions
Which data sources do you work with?
SEC EDGAR, vendor files over SFTP and vendor APIs. Tell us yours and we'll say whether we can take them on.
How do you keep lookahead bias out of backtests?
Every row records when the source made it public, and revisions are new rows. A backtest reads only what was public at the time.
Who runs Deltarecord?
It's a one-person service with a backup engineer on retainer. Your setup keeps running if we stop.
How much does it cost?
We discuss pricing with each firm during the beta.
Private beta
Request early access
We're taking on a few hedge funds, asset managers and family offices.
- Your feeds set up first
- Direct access to the engineer running your setup
- A say in which sources come next