agent · data analysis
NLSQL vs Tilores
55 fields both were evaluated on, 26 of them different — including where one discloses something the other does not. Every value links to the document it came from. 29 further fields are disclosed by neither and are listed at the end rather than tabled.
Assurance
| Field | NLSQL | Tilores |
|---|---|---|
| Audit trail· | no public information nlsql.com · checked Aug 2, 2026 | “Best value picked per field across all linked sources — fully traceable back to the record it came from.”tilores.io · checked Aug 6, 2026 |
| Explainability· | no public information nlsql.com · checked Aug 2, 2026 | “Rules are explicit, tunable, and auditable. You can show exactly why two records were linked.”tilores.io · checked Aug 6, 2026 |
| Compliance certifications· | no public information tilores.io · checked Aug 6, 2026 | |
| 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 | |
| SLA terms· | no public information nlsql.com · checked Aug 2, 2026 | “sub-300ms ingestion (2ms self-hosted), ~150ms query response (1ms self-hosted)”tilores.io · checked Aug 6, 2026 |
| Evaluation coverage· | no public information nlsql.com · checked Aug 2, 2026 | “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 |
Agency
| Field | NLSQL | Tilores |
|---|---|---|
| Operating environment· | “deployed straight to your Azure subscription, with no data ever leaving your infrastructure.”nlsql.com · checked Aug 2, 2026 | “Runs in your cloud, your data centre, or your laptop”tilores.io · checked Aug 6, 2026 |
| Initiative· | “An intelligent agent that autonomously runs analytics, detects anomalies and delivers proactive insights right inside Microsoft Teams & Slack — no manual queries needed.”nlsql.com · checked Aug 2, 2026 | no public information tilores.io · checked Aug 6, 2026 |
Safety
| Field | NLSQL | Tilores |
|---|---|---|
| Safety evaluations· | “Microsoft-certified Enterprise-grade and GDPR-ready”nlsql.com · checked Aug 2, 2026 | no public information tilores.io · checked Aug 6, 2026 |
| Safety policy· | no public information tilores.io · checked Aug 6, 2026 | |
| Third-party evaluations· | no public information tilores.io · checked Aug 6, 2026 | |
| 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
| Field | NLSQL | Tilores |
|---|---|---|
| Pricing model· | no public information tilores.io · checked Aug 6, 2026 | |
| 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· | “Ask in plain English — get queries, data and visualizations in seconds across SQL Server, PostgreSQL, SAP HANA, Snowflake, Redshift, MySQL, Supabase & more.”nlsql.com · checked Aug 2, 2026 | “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 |
| Support model· | no public information nlsql.com · checked Aug 2, 2026 | “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
| Field | NLSQL | Tilores |
|---|---|---|
| Model provider· | no public information tilores.io · checked Aug 6, 2026 |
Ecosystem
| Field | NLSQL | Tilores |
|---|---|---|
| Protocols supported· | no public information nlsql.com · checked Aug 2, 2026 | |
| API access· | “NLSQL Structured databases AI data analytics for structured datasets Natural Language to SQL API.”nlsql.com · checked Aug 2, 2026 | |
| Marketplace presence· | no public information tilores.io · checked Aug 6, 2026 |
Impact
| Field | NLSQL | Tilores |
|---|---|---|
| User base· | “Trusted by data teams at 6,700 + Users on the platform — and growing 1,900 + Monthly active users every month”nlsql.com · checked Aug 2, 2026 | “Used by AI teams, risk teams, and data engineers at MediaPrint, Inato, Grover, and Cofinity-X”tilores.io · checked Aug 6, 2026 |
| Deployment scale· | “Trusted by 6,700+ users across global enterprises”nlsql.com · checked Aug 2, 2026 | “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· | “Healthcare NLSQL for Healthcare AI analytics for ICU and hospital information systems — real-time clinical data access for clinicians, with no SQL required and no data leaving the hospital network.”nlsql.com · checked Aug 2, 2026 | “By Industry Financial Services Insurance E-commerce Logistics Government Security Publishing”tilores.io · checked Aug 6, 2026 |
| High-risk domains· | “Healthcare NLSQL for Healthcare AI analytics for ICU and hospital information systems — real-time clinical data access for clinicians, with no SQL required and no data leaving the hospital network.”nlsql.com · checked Aug 2, 2026 | no public information tilores.io · checked Aug 6, 2026 |
Disclosed by neither
Both NLSQL and Tilores publish nothing on these 29 fields. That is a finding about the category rather than a difference between them, so it is recorded here instead of as 29 identical table rows. Each is shown with its source check on the individual profiles.
- Autonomy level
- Human oversight
- Goal complexity
- Action space
- Documented incidents
- Supported regions
- Base models
- Model swappable
- Open weights
- Fine-tuning
- Context window
- Tool use
- Multi-agent
- Open source
- Red teaming
- Usage restrictions
- Model or system card
- Incident reporting
- Insurance available
- Insurance carriers
- Coverage limits
- Indemnification
- Liability cap
- Tamper-evident log
- Runtime governance
- Permission scopes
- Outcome-based pricing
- Settlement mechanism
- Dispute process