Deployment models
Every SubImage customer gets a dedicated deployment: its own application, databases, and graph. Nothing is shared with other customers. The deployment model decides where that deployment runs and who owns the cloud account.
The three models
SaaS. SubImage runs your deployment in a dedicated AWS account that SubImage owns. You connect your cloud accounts and tools, and SubImage handles everything else.
BYOC (bring your own cloud). SubImage runs your deployment inside your own AWS account or Google Cloud project. Your application data, databases, and files stay in your account. The graph runs on Neo4j AuraDB, a managed Neo4j service, in the same region as your deployment.
BYOC with Private Graph. The same as BYOC, but the graph also runs inside your account, on Neo4j Enterprise servers. Choose this model when your graph data must not leave your account. SubImage approves this plan for each customer.
Compare the models
| SaaS | BYOC | BYOC with Private Graph | |
|---|---|---|---|
| Cloud account | SubImage | Yours | Yours |
| Clouds | AWS | AWS, Google Cloud | AWS, Google Cloud |
| Application, databases, files | SubImage account | Your account | Your account |
| Graph | Neo4j AuraDB | Neo4j AuraDB, same region | Your account |
| Infrastructure cost | Included | Billed to your cloud account | Billed to your cloud account |
| Who operates it | SubImage | SubImage | SubImage |
| Who can freeze changes | SubImage | You | You |
| Setup | Nothing to install | Connect an account | Connect an account |
In all three models, SubImage operates and upgrades the software. In both BYOC models, you own the account, you see every action SubImage takes in it, and you can stop SubImage from changing your infrastructure.
Choose a model
- To start fast with nothing to run, choose SaaS.
- To keep application data in your own cloud account, choose BYOC.
- To keep the graph in your own cloud account too, choose BYOC with Private Graph.
To discuss which model fits your requirements, contact founders@subimage.io.
BYOC documentation
- BYOC architecture: what runs where, and which services your deployment talks to.
- Data protection: roles, data location, and deletion.
- Access and security: the access you grant and how you control it.
- BYOC onboarding: connect your account and create your deployment.
- Operations: upgrades, monitoring, sizing, and offboarding.