Skip to main content

Managing a vector database on AWS is expensive and time-consuming

SvectorDB is the service AWS should have built. A truly serverless vector database, and significantly more cost-effective

No credit card required

The Existing Options

OpenSearch

AWS's open source fork of ElasticSearch

RDS

Managed SQL service with Aurora, MySQL, and PostgreSQL

MemoryDB

Redis-like service designed for persistence

DocumentDB

MongoDB-compatible document database

ServiceScales to zeroPay per requestManagedConsistencyMinimum cost
OpenSearchEventual$76.65 / month
OpenSearch "Serverless"Eventual$700 / month
RDSEventual / Immediate$211.7 / month
MemoryDBEventual / Immediate$225.57 / month
DocumentDBEventual$191.99 / month

* Minimum cost is based on a single instance of the smallest non-burstable (t2/t3/t4) size available

There's no serverless options

For vector databases on AWS, you're forced to choose between expensive managed services or self-managed solutions. There's no Lambda or DynamoDB-like solutions

What SvectorDB does differently

Scales to zero

Only pay for what you use, with no minimum fees or upfront costs

Pay per request

Predictable pricing, based on the number of requests you make

Managed

No need to worry about scaling, provisioning or maintenance

Immediate consistency

Changes are reflected instantly, no more bad user experience

It's built specifically to work with AWS

Native CloudFormation support, built to integrate seamlessly with your existing AWS infrastructure

Resources:
VectorDb:
Type: SvectorDB::VectorDatabase::Database
Properties:
IntegrationId: <INTEGRATION_KEY> # Replace with your integration key
Name: My first database
Metric: EUCLIDEAN
Dimension: 1024
Type: SANDBOX
ApiKey:
Type: SvectorDB::VectorDatabase::ApiKey
Properties:
IntegrationId: <INTEGRATION_KEY> # Replace with your integration key
DatabaseId: !Ref VectorDb
MyLambdaFunction:
Type: AWS::Lambda::Function
Properties:
Handler: ...
Role: ...
Code: ...
Runtime: ...
Environment:
Variables:
SVECTORDB_API_KEY: !Ref ApiKey

Our SDKs are all generated using Smithy. If you're familiar with AWS SDKs, you'll feel right at home

// Create or update an item
client.setItem({
databaseId,
key: 'abc',
value: Buffer.from('Hello world!'),
vector: [0.1, 0.1, 0.1, 0.1],
metadata: {
'title': {string: 'Backend Developer'},
'tags': {stringArray: ['backend', 'javascript']},
'salary': {number: 25000}
}
});

// Query based on a vector
client.query({
databaseId,
query: {
vector: [0.5, 0.5, 0.5, 0.5]
},
filter: 'salary:>12000'
});

// Query based on key (nearest to existing vector)
client.query({
databaseId,
query: {
key: 'abc'
},
filter: 'tags:javascript'
});

The benefits

Metadata Filtering

Use Lucene / ElasticSearch style queries to filter results based on key-value pairs

Instant updates

Upserts and deletions are reflected instantly, no need to worry about eventual consistency

Natively Serverless

Pay per request based pricing, with no provisioning or scaling required

CloudFormation Support

Integrate SvectorDB into your existing CloudFormation templates

Built-in Vectorizers

Use our built-in vectorizers for text and images, or bring your own embeddings

Pay per request

Only pay for the requests you make, with no minimum fees or upfront costs

The drawbacks

We're a micro start-up, and our philosophy centers around transparency. When you reach out to us, you're talking to the people who built the product, not navigating through layers of support agents. In the spirit of transparency, our weaknesses:

Snapshots

While we maintain our own internal backups to protect against data loss, we do not offer the ability to create snapshots of your databases.

Max record limits

To ensure consistent performance, we have a default limit of 1 million records per database. This limit can only be increased by contacting support.

Company Size

We're a micro start-up, while we consider it a benefit as we're hyper-responsive to customers needs, it may be a concern for some customers.

Performance

Wikipedia Embeddings

1 million

vectors

768

dimensions

9ms

query latency (average)

97.4%

recall @ 32

Use Cases

Recommendation Engines

Using vectors to represent items and users, recommendation engines leverage vector similarity to suggest relevant items to users based on their preferences.

Document / Image Search

Transforming documents and images into vectors enables deep meaningful search capabilities by leveraging semantic and visual similarities.

Retrieval Augmented Generation

Augmenting generative models with context enhances the quality of generated content, presenting a more refined and contextually relevant output.

Pricing

Storage

$0.25 / GB / month

The total size of your database and indexes, including keys, value, and vectors.

Queries

$5 / million

A single query counts as 1 read operation, regardless of the number of results returned or data scanned.

Writes

$20 / million

A single put or delete call counts as 1 write operation, regardless of the size of the item.

Free Tier

5k records

Create up to 10 free tier indexes of up to 5k records, with no time limit.

SvectorDB has a free tier to allow for experimentation and prototyping

Price Comparison Calculator

Queries per month

Writes per month

Vector Dimension

Vectors Stored

SvectorDB

$7.25/m

Pinecone

$83.44/m

SvectorDB calculations
FeatureAmountUnitsCostTotal
Queries1m1 Read Operation$5 / million$5.00
Writes100k1 Write Operation$20 / million$2.00
Storage500k vectors~1.018 GB$0.25 / GB$0.25
$7.25
Pinecone calculations
FeatureAmountUnitsCostTotal
Queries*1m10 Read Units$8.25 / million$82.50
Writes100k3 Write Units$2.00 / million$0.60
Storage500k vectors~1.018 GB$0.33 / GB$0.34
$83.44

* Fetching 32 nearest neighbours and returning metadata

Ready for the database AWS should have built?

No credit card required