Deploy where your data
is allowed to be
Tilores is AWS-native by default and infrastructure-agnostic by design. The same entity resolution engine runs wherever you need it, on whatever you already run.
Software you operate, not a service that holds your data
Four ways to run Tilores
AWS is the default, the easiest path, and the right choice for most customers. The other three exist for teams whose data cannot leave a particular perimeter.
Managed Cloud on AWS
Tilores runs in our AWS account — fully managed, zero infrastructure for your team to operate. Available through the AWS Marketplace, in any AWS region. This is the easiest path and the right one for most customers.
- Available on AWS Marketplace
- Fully managed by Tilores
- Any AWS region
- Serverless — scales automatically
- SOC 2 certified
- No infrastructure to manage
Your AWS Account
The same deployment, inside your own AWS account. It runs on DynamoDB, SQS, and S3 in your VPC. Your data never leaves your environment and no Tilores staff can access your records. We manage and update the deployment remotely; the infrastructure is yours.
- Data stays in your AWS account
- Available on AWS Marketplace
- Any AWS region
- Same features as Managed Cloud
- Full visibility and control
- SOC 2 certified
- Suits sensitive or regulated data
Another Cloud
The same engine deploys to any other cloud, using whatever key-value store, queue, and object storage you already run there. Same matching rules, same GraphQL API, same audit trail.
- Runs on your existing KV store, queue, and object storage
- Data stays in your cloud account
- Same features as Managed Cloud
- Meets regional data residency requirements
- Same matching rules and GraphQL API
On-Premise
The same engine, deployed inside your own infrastructure. For organisations with air-gapped environments, strict data sovereignty requirements, or existing on-premise investment.
- Full data sovereignty
- Air-gapped environments supported
- Runs on your existing KV store, queue, and object storage
- Same matching rules and GraphQL API as cloud
- Custom SLAs
- Onboarding and professional services
Three components. Any infrastructure.
Tilores is portable because it asks for very little. The engine depends on three generic things, and any products that fill those roles will do.
Holds the entity graph and the record index. Any key-value store with the same access pattern can take its place.
Carries ingest and re-assembly work between components. Any queue that guarantees delivery can take its place.
Holds bulk input, exports, and snapshots. Any object or file store can take its place.
There is no fourth requirement. No proprietary database, no vendor-specific runtime. That is why the same build runs on AWS, on another cloud, in your own data centre, or on a single machine with no network access at all.
Same software, wherever it runs
There is no cut-down self-hosted edition and no cloud-only feature set. The deployment model changes who operates the infrastructure and where the data sits. It does not change the product.
That matters in practice: the matching rules you tune during evaluation in Tilores Studio are the rules that run in production, on whichever infrastructure you choose. There is no migration step and nothing to relearn.
- The matching rules you configure
- The GraphQL API your applications query
- Tilores Studio as the interface
- Data provenance on every record
- Automated retention and cascading deletion
- The full audit trail of queries, exports, and deletions
- Explainable matches you can show a regulator
The honest comparison
Latency figures are typical, not contractual. Query and ingestion times on AWS include the API round trip; self-hosted figures are measured next to the workload.
The proof runs on your laptop
You do not have to take the portability claim on trust. Tilores Studio runs the full engine on your own machine, with no signup, no licence key, and no network egress. It is the same engine that runs in production on AWS, on your own infrastructure, or in an isolated network.
Free. 100,000 records in local mode.
Tell us where your data has to stay
30 minutes with our team. We will scope a deployment that fits your regulatory and infrastructure constraints, and walk through the platform with your data.