01 Dedicated resources
Capacity for your application.
Run on dedicated compute and storage. Size the instance around your records, indexes, query mix and expected concurrency.
Explore configurationsEnterprise
Your workload.
Your operating requirements.
Build on a multimodal database with dedicated resources. Bring your data, deployment requirements and success criteria. We’ll work through the configuration with your team.
Dedicated deploymentYOUR ENVIRONMENT
Your applicationBuilt around your data.
Your selected region
OriginChainDBSingle tenant
SQLVectorGraphFull-text
ComputeDedicated capacity
StorageDedicated volumes
AccessRecoverySupport
Built around your business
The resources you need.
A foundation you understand.
Choose the database configuration for the work it needs to do, from application queries to retrieval and connected records.
02 Regional deployment
A region you can plan around.
Choose a supported region for your database and its backups. Discuss network access and any private deployment requirements with the team.
Review deployment options 03 Multimodal database
One engine. More ways to build.
Use SQL, vector, graph and full-text interfaces for your workload. Connect the supported tools and SDKs your developers already use.
Explore the productProduction planning
Make recovery part
of the deployment.
Availability and recovery solve different problems. Set the expectations for each before your application goes live.
Read the operations guideChoose the standby configuration.
An optional warm standby follows the primary in the same region. Replication is asynchronous; recent writes can be missing after an abrupt primary failure. Promotion is operator-driven by default.
Replication behaviourStart with a tested backup path.
Dedicated configurations include encrypted daily storage snapshots in the instance’s region. Restore into a fresh instance and verify application-critical data before switching traffic.
Backup & restoreAgree the operating relationship.
Discuss support coverage, escalation contacts and availability commitments with the team. The deployment agreement defines the services and terms for your environment.
Plan support coverageArchive streaming and point-in-time recovery remain in preview. Current recovery planning should use daily snapshots; review the documented limits for your instance.
Ready for the review
Give each team
a clear starting point.
Bring security, engineering and procurement into the conversation early. Work through the requirements that affect your deployment.
01
Security & data protection
Review controls, security programs in progress, the data processing agreement and the requirements for your data.
Security overview 02
Architecture & recovery
Confirm the topology, backup approach, promotion procedure and recovery expectations for your configuration.
Architecture overview 03
Commercial terms & support
Agree capacity, availability commitments, support coverage and any private deployment scope in your agreement.
Discuss your requirementsFrom evaluation to production
Prove it with
your own workload.
Start with representative data and the queries your application depends on. Agree what a successful evaluation looks like before choosing the final configuration.
Review the benchmark methodology-
Describe the workload.
Share data volume, query patterns, peak concurrency, required tools and your region preferences.
-
Evaluate the configuration.
Test representative reads and writes. Review latency, resource use, access controls and recovery with your engineering team.
-
Agree the path to launch.
Confirm sizing, migration steps, operating responsibilities and commercial terms before moving production traffic.
Before we begin
A few practical questions.
Can I begin on a free database?
Yes. Use the free configuration to explore the database, then evaluate dedicated resources for your production requirements. Shared and dedicated configurations have different capacity, connectivity and recovery options. Compare pricing and configurations.
Can we discuss a private deployment?
Yes. Managed deployment in a supported region is the standard starting point. Private deployment requirements are scoped with the team; availability, responsibilities and commercial terms depend on the engagement.
What should we bring to a technical walkthrough?
A description of your data, representative queries, expected traffic, preferred region and any security or recovery requirements. Include the tools you need to connect and the measurements you want to validate.
Where can our security team start?
Start with the security overview and authentication guide. Contact the team to discuss planned assessment scope, a security questionnaire and the documentation needed for your review.
Build with OriginChainDB