Tilores
17 fields evidenced · 42 with no public information. Every value below links to the document it came from and the date we checked it.
17 of them are quoted but not yet interpreted: we hold the source sentence and the date we read it, but nobody has written the answer to the question yet. Those rows show the quote and say so rather than repeating it back as an answer. Why these exist
Trust gap
How this is scoredThese scores are automated. A 1 or 2 counts how many fields this entry answers with a citation — not what those answers say. A 0 means every field for that dimension is recorded as undisclosed and none of the pages we captured mentions it. No one has scored this entry against the rubric yet.
Are scope, spend, and authority enforced while the agent runs?
Is there a tamper-evident record of what it actually did?
Are compliance obligations attached per engagement?
Scored from 1 evidenced field(s): regulatory_alignment. Automated score; capped at 2 pending review.
Counts Regulatory alignment, each cited below.
Does payment depend on a verified result?
Can the deployment be insured, and is the customer indemnified?
Assurance
- Insurance available
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Own liability cover
- no public informationtilores.io · checked Aug 13, 2026 · source did not state this
- Insurance carriers
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Coverage limits
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Indemnification
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Liability cap
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Audit trail
“Best value picked per field across all linked sources — fully traceable back to the record it came from.”
tilores.io · checked Aug 6, 2026- Tamper-evident log
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Explainability
“Rules are explicit, tunable, and auditable. You can show exactly why two records were linked.”
tilores.io · checked Aug 6, 2026- Runtime governance
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Permission scopes
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Compliance certifications
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Regulatory alignment
“Rules are explicit, tunable, and auditable. You can show exactly why two records were linked. You can adjust precision and recall to fit your use case. No black box.”
tilores.io · checked Aug 6, 2026- Outcome-based pricing
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Settlement mechanism
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Asset custody
- no public informationtilores.io · checked Aug 13, 2026 · source did not state this
- Dispute process
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- SLA terms
“sub-300ms ingestion (2ms self-hosted), ~150ms query response (1ms self-hosted)”
tilores.io · checked Aug 6, 2026- Evaluation coverage
“They evaluated Tilores against multiple alternatives across a two-month structured benchmark. Tilores won on the hardest data to match: the global shipping and customs records that competing solutions couldn't reliably resolve.”
tilores.io · checked Aug 6, 2026- Self-reported performance
- no public informationtilores.io · checked Aug 13, 2026 · source did not state this
Agency
- Autonomy level
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Human oversight
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Goal complexity
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Action space
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Operating environment
“Runs in your cloud, your data centre, or your laptop”
tilores.io · checked Aug 6, 2026- Initiative
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
Safety
- Safety evaluations
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Red teaming
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Safety policy
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Usage restrictions
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Model or system card
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Incident reporting
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Third-party evaluations
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Data handling
“Tilores deploys inside your own environment, so the resolved entity graph your models retrieve from never leaves it.”
tilores.io · checked Aug 6, 2026
Practicality
- Pricing model
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Price point
“Tilores Studio Free Run entity resolution locally — up to 100,000 records.”
tilores.io · checked Aug 6, 2026- Availability
“Tilores Studio is now available. Run entity resolution locally on your machine. Download free →”
tilores.io · checked Aug 6, 2026- Deployment options
“AWS-native by default · Infrastructure-agnostic by design · Runs in your cloud, your data centre, or your laptop”
tilores.io · checked Aug 6, 2026- Integrations
“GraphQL ● 96ms query ResolveEntity { entity(input: { id: "ent_3c8b21a0" }) { entity { id score edges recordInsights { name: valuesDistinct(field: "name" ) email: valuesDistinct(field: "email" ) phone: valuesDistinct(field: "phone" ) dob: valuesDistinct(field: "dateOfBirth" ) address: valuesDistinct(field: "address" ) location: valuesDistinct(field: "location" ) } } } }”
tilores.io · checked Aug 6, 2026- Supported regions
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Support model
“Our team works that way by default. "The Tilores team is one of the most professional teams I've ever worked with in my professional career. They were 100% supportive. They really were part of our team - it felt like a family. They are highly accessible, very professional. They can have discussions at a very pedantic technical level and they're more than capable of explaining things at a business level when needed."”
tilores.io · checked Aug 6, 2026
Foundation models
- Base models
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Model provider
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Model swappable
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Open weights
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Fine-tuning
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Context window
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
Ecosystem
- Protocols supported
“GraphQL ● 96ms query ResolveEntity {”
tilores.io · checked Aug 6, 2026- Tool use
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Multi-agent
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- API access
“GraphQL ● 96ms query ResolveEntity {”
tilores.io · checked Aug 6, 2026- Open source
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Marketplace presence
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
Impact
- User base
“Used by AI teams, risk teams, and data engineers at MediaPrint, Inato, Grover, and Cofinity-X”
tilores.io · checked Aug 6, 2026- Deployment scale
“110M+ Source records resolved 60M Resolved entity clusters <24h Time to first results 100ms Query latency at scale”
tilores.io · checked Aug 6, 2026- Target sectors
“By Industry Financial Services Insurance E-commerce Logistics Government Security Publishing”
tilores.io · checked Aug 6, 2026- High-risk domains
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Documented incidents
- no public informationtilores.io · checked Aug 6, 2026 · source did not state this
- Market recognition
- no public informationtilores.io · checked Aug 13, 2026 · source did not state this
Compared with
Side-by-side on the fields where Tilores and the other entry are both on record and actually differ.