What it is
Embeddable B2B AI infrastructure. Developers integrate conversational AI into their own product through an API, in the same role as Stripe or Twilio. It also runs as a self-serve SaaS โ an embedded widget added with one line of JavaScript, or a standalone URL. Both share one foundation.
How it differs from RAG
Knowledge is stored as structured plain text and interpreted at query time. No vector database, no embedding step, no re-ranking.
Three roles
MCP
A remote MCP server is included, so external AI agents can query a knowledge base directly โ by OAuth as a custom connector, or with a bearer API key. One tool is exposed, vates_ask, and it is read-only: it cannot change settings, read conversation logs, or reach other instances. Access is revocable from the console.
Operations
Setup, instance settings, the knowledge base, billing and security are all operable from a phone. Hash-chained tamper-evident audit logs, passkeys, 2FA, per-customer IP allow/denylists, per-instance rate and consumption limits, encrypted daily backups, and an automated data-retention lifecycle.
Pricing
Deposit-based. No subscription, no monthly fee, no minimum spend. Usage is deducted from a prepaid balance; minimum top-up is USD 5.00.
A startup from Okayama, Japan that is founded by Shuji Yamashita, Takuya Aoki.
Retrieval
Direct observation of structured plain text โ no embedding or re-ranking step
Knowledge updates
Effective the moment a line is written; no re-indexing
Knowledge visibility
Plain text, readable and auditable directly
Deployment
Embedded widget (one line of JS) or standalone URL
API
REST with idempotency keys and per-tenant rate limits
MCP server
Remote, OAuth or API key; read-only vates_ask tool
Input formats
Text, logical notation, images and PDFs
Reply language
Answers in the reader's own language
Audit Log
Hash-chained, tamper-evident, CSV export
Billing
Prepaid deposit, no subscription, no monthly fee
Authentication
Passkeys (WebAuthn/FIDO2), 2FA, JWT with session ledger
Access Restrictions
Per-customer IP allowlist and denylist, CIDR ranges
Knowledge is held as structured plain text and interpreted at the moment it is queried. There is no vector database, no embedding step, and no re-ranking. A line written into the knowledge base takes effect immediately, with no re-indexing, and the contents stay readable โ you can see exactly what the system holds, and delete a line and verify it is gone.
Fewer moving parts. No vector database to run, no GPU, no per-use embedding API โ which lowers both cost and the number of things that can break. Nothing is hidden behind numeric vectors, so answers can be traced to the material behind them. Billing is a prepaid deposit with no subscription and no monthly fee, so it can be tried at small scale and grown without renegotiating a contract.
Two groups. Developers who want to embed conversational AI into their own product through an API, in the same role as Stripe or Twilio. And small to mid-sized businesses that want to run it out of the box โ as a widget on their site or a standalone chat โ without engineering work. Both are served by the same foundation.
Python and FastAPI on the backend, React with Vite on the front end, SQLite for storage, on Ubuntu with Nginx. Payments through Stripe. Deployed on AWS EC2 behind Cloudflare. Notably absent: there is no vector database and no embedding pipeline in the stack.
VATES is built by STANDOUT Inc. in Okayama, Japan, on a theory its developer worked out independently rather than assembling from existing frameworks. The premise is that meaning is not fixed in a symbol but arises when something is observed โ so knowledge is kept as structure and interpreted at read time rather than compressed into coordinates in advance.
A concise formulation has been published as a preprint, IIIS: An Inter-Intelligence Intermediary Syntax for Shared Observation Across Perceptions (https://doi.org/10.5281/zenodo.21374493). The full theory is being prepared as a book.
The three working roles are named after the Celtic oral tradition: bard receives, druid keeps, vates speaks across.
We have collected here some useful links to help you find out if VATES.jp is good.
Check the traffic stats of VATES.jp on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of VATES.jp on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of VATES.jp's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of VATES.jp on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about VATES.jp on Reddit. This can help you find out how popualr the product is and what people think about it.
Do you know an article comparing VATES.jp to other products?
Suggest a link to a post with product alternatives.
Is VATES.jp good? This is an informative page that will help you find out. Moreover, you can review and discuss VATES.jp here. The primary details have been verified within the last quarter. So they could be considered up to date. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.