Find the answer.
Follow the details.

OriginChainDB is a distributed multimodal database for SQL records, vector search, full-text search and graph relationships. Ask adds a natural-language query interface over the engine. Explore the database.

A provisioned database has an HTTPS endpoint and credentials for its supported API surfaces. Free uses shared infrastructure; dedicated configurations have their own compute and storage. Review the selected configuration and follow the quickstart for your first request.

Free includes 1 GB of database storage. Two pooled configurations are available: $29/month for 25 GB storage and 20 GB monthly data transfer, or $49/month for 50 GB storage and 50 GB transfer. Dedicated pricing depends on resources, region and options. Compare configurations and estimates.

Check the regions available for the configuration you select in the console. Dedicated database resources are provisioned in the selected region; account and billing services are global. The pooled configurations are scoped to India (Mumbai). Read the deployment guide.

Create an account at app.originchaindb.com, select an available configuration and review its requirements. Once provisioned, use the instance endpoint and credential from the console. Keep credentials on your server and follow the first-query guide.

The public website at originchaindb.com and the authenticated console at app.originchaindb.com are separate applications. Use the website for product information and documentation, and the console for your account and instances.

Use Free for learning and prototypes. The 25 GB and 50 GB pooled configurations provide fixed monthly shared capacity; choose your configuration in the console. Choose a dedicated configuration when you need your own compute and storage, with recovery and standby options reviewed separately. Compare the current options.

The four data models are SQL records, vectors, full-text indexes and graph relationships. Ask is a natural-language interface, not a fifth storage model. Each API has its own supported operations and limits; the documentation shows the request and result shapes.

Atomicity applies to the writes included in a supported operation or transaction. A row update does not automatically update a separately written vector or full-text index. Coordinate those index writes in your application and use stable record IDs to connect results. See transaction guarantees and full-text indexing.

Dedicated configurations can use a primary and optional standby with asynchronous replication. The primary accepts writes; promotion and availability depend on the configured topology. This is not a promise of quorum commit or multiple active writers. See replication and recovery behavior and your service agreement.

Yes. Use the same stable ID for a SQL row and its vector entry, then fetch the row for a returned search ID. The vector is written through its own API; changing the row does not automatically regenerate its embedding. See how vector entries relate to rows.

Ask first tries a deterministic grammar against the schema catalog. If that cannot resolve the question, it uses the configured LLM; a compiled plan can then be cached. Pass a schema scope and use show_plan to inspect the result. Schema changes can invalidate cached plans. Read the Ask reference.

Ask can fall back to the LLM configured for the instance. Review the provider, credential handling and provider terms before enabling that path. The deterministic grammar and plan cache can answer supported requests without a new LLM call. See how Ask chooses its path.

An Ask question is sent to the configured LLM when the deterministic path needs that fallback. Do not include secrets or sensitive personal data in the question. Review the configured provider and data handling requirements rather than assuming every external inference call stays in the database region. Read the request guidance.

Yes. Declare relations on registered tables, then follow connected records or use supported graph algorithms. Cypher and algorithm endpoints have different syntax, limits and result shapes; supported Cypher is a subset. Review traversal examples and limits.

The HTTP API uses Unicode tokenization and lowercase normalization across scripts. Engine stemmers and other analyzer stages are not all selectable through the API: do not assume stemming, lemmatization or accent folding is enabled. Check the live analyzer behavior and synonym support.

Single-row writes are atomic. The preview /tx API defaults to snapshot isolation with commit-time conflict detection and an optional serializable mode; SQL session transactions use read committed with different conflict behavior. Pick the surface for your workload and handle commit failures explicitly. Compare the two transaction APIs.

Latency depends on query shape, data size, indexes, hardware, load and network distance. Measure the full request path on your own dataset; a published benchmark is evidence for its stated setup, not a latency guarantee for every configuration. Review the benchmark methods and results.

A cache hit, a fresh grammar compilation and an LLM fallback have different costs. Inspect the cache field and query plan, then measure the path your application uses. There is no single response time that covers all three. See plan-cache behavior.

Vector accuracy and latency depend on the index, dimensions, metric, filters and search settings. Compare recall and tail latency together using a representative query set; fast and high_recall modes make different tradeoffs. Read published measurements and choose search settings.

Use the configuration estimator for capacity planning, then benchmark your workload with representative concurrency, writes and queries. Sizing estimates are not measured throughput guarantees, and adding a standby does not imply linear query scaling. Review the benchmark resources.

Capacity depends on vector dimensions, metadata, the index representation and available memory and storage. A documented index option does not establish measured performance at every corpus size. Review the index choices and discuss a representative capacity test.

Dedicated configurations include a daily storage snapshot. Snapshot recovery and continuous archive are separate paths; the operations guide documents current archive limitations. Free and pooled configurations do not include point-in-time recovery. Review backups and recovery expectations.

Continuous archive and restore-to-timestamp options for dedicated configurations are in preview. The operations guide records lagging or stalled archive progress, so do not treat sub-second or per-second recovery as delivered behavior. Plan against the available daily snapshot and review your recovery requirements with the team. Read the current recovery caveats.

A configured standby follows the primary asynchronously, so abrupt primary loss can lose recent acknowledged writes. Promotion is fenced by the writer lease; automatic promotion is opt-in and depends on the configured path and catch-up state. A standby does not replace a backup. Read the failover procedure and durability caveats.

Health and readiness endpoints expose instance status; the usage endpoint reports per-tenant counts and activity. SQL EXPLAIN helps inspect query plans, and the operations guide describes tracing and monitoring options. Confirm the signals available on your deployed configuration. Explore operational monitoring.

Python, TypeScript and Go clients cover different parts of the HTTP API. Python has the widest coverage; TypeScript also offers a control-plane client, while Go covers query surfaces. Use plain HTTP for operations your chosen SDK does not wrap. Compare the client coverage.

The HTTP reference documents a watch interface for change notifications. Check its supported subscription scope, delivery behavior and client handling before using it to keep another system in sync. Do not assume it is a durable replay log or a universal CDC replacement. Read the HTTP API reference.

Dedicated configurations have their own compute and storage. Free and the $29 and $49 pooled configurations use shared infrastructure. Database isolation, network paths and access controls should be evaluated for the chosen deployment. Review the deployment boundaries.

Managed public endpoints use HTTPS. The security page describes where TLS terminates and how the network path differs between shared and dedicated deployments. Review storage, backup and key-management requirements for your selected configuration. Read the security overview.

Review which identity, request and outcome fields your deployed service records, where you can access them, and the retention or export options in your agreement. Console preview screens alone do not establish live audit coverage. Review access and operational records.

Contact security@originchain.ai for current assessment status, questionnaires and contractual requirements. A database feature is not a compliance certification; evaluate the deployment and applicable agreement for your workload. Review the published security information.

Dedicated database resources are provisioned in the selected region. Account and billing are global services; external LLM providers and other integrations have their own data paths. Confirm database, backup and integration requirements together for your deployment. Read the deployment guide.

The dedicated estimator includes the four data models without separate model fees. Resource sizing, standby, recovery, networking and other agreed options affect the configuration. Confirm the available capabilities and final quote before launch. Review the configuration options.

Commercial timing follows the applicable agreement; the published Terms distinguish immediate upgrades from next-cycle downgrades. Do not assume all changes are available in place or have no interruption. Free, pooled and dedicated configurations currently do not support in-place switching between them. Review the Terms and discuss a change.

Contact the team to agree a billing term or custom commitment. The public estimator shows a monthly equivalent and does not apply an automatic annual discount. Discuss commercial terms.

The $29 configuration includes 25 GB storage and 20 GB monthly transfer; the $49 configuration includes 50 GB storage and 50 GB monthly transfer. Check current usage limits and billing terms in the console before purchasing. For other configurations, review included usage and the final agreement. See current allowances.

Enterprise is scoped around your deployment, network, region, recovery, support and contractual requirements. Confirm each capability and service commitment with the team rather than assuming a preset package or an unshipped topology. Discuss a custom deployment.

The dedicated pricing estimator includes SQL, vector, graph and full-text without separate per-model fees. Rows and indexes still consume compute, memory and storage, so workload size affects the estimate. Size a configuration.

The current shared options are Configuration 25 GB pooled at $29/month with 20 GB monthly transfer, and Configuration 50 GB pooled at $49/month with 50 GB transfer. Both are monthly USD configurations with shared compute. Select a configuration in the console and review checkout before paying. See the current configuration names and limits.

The public estimator starts at $320/month for a Mumbai baseline with 2 vCPU, 8 GB RAM and 20 GB storage. This is a planning estimate in USD before applicable taxes; availability and the final quote are confirmed before launch. Review and adjust the estimate.

Review a dedicated configuration when you need more capacity or dedicated resources. In-place switching from pooled to dedicated is not currently available; plan the data movement and application cutover with the team. Discuss the deployment path.