Automatic repair
Repaired automatically.
A failed run is detected, the pipeline is repaired and the schedule resumes. Each repair ships as a new version; you see what changed and when.
Reliable datasets, scoped to your brief.
We build the pipeline, run it on your schedule and repair it when a source changes. Your team receives verified rows where it already works — Sheets, Snowflake, S3, API or MCP.
Three things define your dataset.
We scope all three with you before the first run.
- 01
Coverage
The sources, markets and mobile apps it draws from.
- 02
Depth
The fields, matching rules and checks that make every row usable.
- 03
Frequency
How often it refreshes and where each run delivers.
One pipeline, end to end.
- 01 / Sources
Products & sourcesYour market, defined
- 02 / Collect in parallel
Read public websitesPrices, stock, promotions
Read mobile appsOffers and availability
- 03 / Process & verify
Match & compareSame products, new snapshot
- 04 / Publish
Market pricesA dataset that stays current
Email reportSnowflakeXLSX
Websites and apps read in parallel. Products matched; every published row passes type, null and duplicate checks. Delivered to Snowflake, XLSX or an email report.
Escalation
A human when repair stops.
Some failures need investigation. Your agreement names the escalation contact, coverage hours and response times. An unverified fix is not a completed recovery.
Continuity
Code you can leave with.
Enterprise agreements can include a perpetual licence to your pipelines’ Python source: a snapshot as deployed when you leave, with dependencies and handover notes, to run and modify for your own use. The licence outlasts the contract. Repairs and updates stop at exit, because keeping pipelines working is the service.
Security review
Security and data handling.
Everything your security, legal and procurement teams will ask about, with the document each answer comes from.
SOC 2 Type IIIndependently audited
GDPRDPA & SCCs available
EU AI ActTransparency built in
Independent assuranceSOC 2 Type II audited; report scope, period and findings available for your security review.
Review the report’s scope, period and findings with your security team. Request the SOC 2 report →
Collection scopeSources, fields, intended use and frequency agreed in writing; you confirm authority to access and use the data.
Sources, fields, intended use and frequency are agreed in writing. You confirm your authority to access and use the requested data. Access terms →
Permitted accessRobots.txt respected on websites; no gated content without your credentials, used within account permissions.
Pipelines respect robots.txt on websites and do not access content behind logins or paywalls except where your agreement provides for it. Authenticated collection uses your credentials, within your account’s permissions. Access terms →
Personal dataPseudonymisation and filtering of personal-data fields configured per agreement; your data is not reused, sold or exploited for Jsonify’s purposes.
Pseudonymisation and filtering of personal-data fields are configured per agreement; where configured, they run on every row. Data processed on your behalf is not reused, sold or exploited for Jsonify’s purposes. Privacy policy →
Hosting and transfersHosting, subprocessors, retention, deletion and international transfers are covered in your review.
Hosting, subprocessors, retention, deletion and international transfers are covered in the review. Subprocessors → Privacy policy →
Procurement
Four steps to a first production run.
Bring your security questionnaire. We work through it with your security, legal and procurement teams.
- 01
Security evidence
SOC 2 report and the controls relevant to your service.
- 02
Data and access scope
Sources, access method, fields, intended use, delivery destinations.
- 03
Processing terms
Roles, contractual terms, data handling, transfers.
- 04
Operating agreement
Validation criteria, support, and how changes to the pipeline are handled.
Questions before you get started.
Why not use a managed collection service?
Jsonify offers managed collection alongside self-serve. We agree the sources, fields, checks, schedule and delivery with you, then build, run and repair the pipeline. Your agreement sets out support and how changes are handled. See how we scope your dataset →
Can we keep our existing proxy or browser provider?
An infrastructure contract and a maintained dataset solve different parts of the job. Keep the infrastructure that works for your team, and discuss how it fits into the collection and delivery scope before rollout. Compare infrastructure and dataset responsibilities →
What happens to our data if we stop using Jsonify?
You can export your datasets. Enterprise agreements can also include a perpetual licence to a snapshot of your pipeline code as deployed at exit, for your own internal use, with dependencies and handover notes. Repairs and updates stop when the agreement ends. Review continuity and vendor risk →
How does Jsonify handle security and compliance?
Jsonify is SOC 2 Type II audited, offers a GDPR Data Processing Addendum with Standard Contractual Clauses, and discloses Jason as an AI system in line with the EU AI Act. Pseudonymisation and filtering of personal-data fields can be configured per agreement. For a managed deployment, we agree collection scope, processing terms and delivery requirements, and provide the SOC 2 report for your security review. Explore enterprise security and compliance →
Two ways to collect your market.
RadarNow available
Monitor what’s published.
Collect prices, menus, listings and availability from websites and apps. Follow what changes across sources and markets.
Radar · Supermarket prices
Greenway
Hartwell’s
Fresco
Marlow Market
Pantry & Co
Corner Store
BenchmarkEnterprise
Compare what’s offered.
Run defined scenarios through forms to collect comparable insurance quotes, rental rates and personalised offers.
Benchmark · Motor quotes
Enterprise
Let’s scope your dataset.
Share your sources, delivery needs and security requirements.