Private AI on Your Own Server
Get AI answers from your database or Odoo when your data rules do not allow processing on someone else's platform. STYD installs a private assistant on your own server, tunes it to your schema and business rules, and hands it over.
STYD installs a private AI assistant on the client's own Linux server, connected read-only to PostgreSQL, MySQL, or Odoo 15 to 20 and tuned to their schema and business rules. STYD hosts nothing; the AI is the client's own OpenAI or Azure OpenAI account, or a local open model on their hardware.
The problem
Your company wants AI answers from its database or Odoo, but its data must not be processed on someone else's platform — because of regulation, client contracts, or internal policy.
Who it's for
Companies with strict data rules — finance, health, legal, public sector, and EU companies — running PostgreSQL, MySQL, or Odoo 15 to 20.
The outcome
Your team asks questions in plain language and gets answers grounded in your real data, from an assistant that runs on a server you control, with the AI provider chosen by you.
What STYD delivers
STYD builds a private AI assistant on the STYD engine, installs it on your own Linux server, connects it read-only to your database or Odoo, tunes it to your schema and business rules, tests it on your real questions, and hands it over with guidance. STYD hosts nothing. You choose the AI behind it. Option 1: your own OpenAI or Azure OpenAI account, under your own contract (Azure can keep processing in an EU region) — the best answer quality. Option 2: a local open model on your own hardware, so data never leaves your infrastructure — lower answer quality, it needs suitable hardware (GPU), and it is scoped case by case.
Common questions this service helps with
- private AI on our own server
- self-hosted AI assistant for business database
- AI assistant on-premises PostgreSQL
- private AI for Odoo on own server
- AI on our data without a third-party platform
- local LLM for business database
Pricing
Final pricing is confirmed after a short scoping conversation.
FAQ
The assistant itself — the application, its setup, and its connection to your database or Odoo — runs on your own Linux server, and STYD hosts nothing. Where the AI model runs depends on the option you choose: your own OpenAI or Azure OpenAI account, or a local open model on your hardware. Only the local model keeps every step, including the AI, on your own infrastructure.
Two options. With your own OpenAI or Azure OpenAI account, you hold the contract with the provider directly, and Azure can keep processing in an EU region; this gives the best answer quality. With a local open model on your own hardware, data never leaves your infrastructure; answer quality is lower, it needs suitable hardware (GPU), and it is scoped case by case.
No. The assistant connects with read-only access to your database or Odoo. It answers questions; it does not write to your systems.
With your own OpenAI or Azure OpenAI account, that depends on the provider's terms, which you sign with them directly and which can be reviewed during scoping. With a local model, your data is never sent to a provider, so it is never used for training.
A Linux server or VM, read-only access to your database or Odoo, an AI account (OpenAI or Azure OpenAI) or suitable hardware for a local model, and examples of the questions your team actually asks.
Related STYD services
Give your team a private AI assistant that understands your database and business rules, so everyday questions about sales, customers, invoices, and operations get answered in minutes instead of waiting on reports.
Make Odoo AI reporting match how your company actually works, not only generic Odoo data.
Turn scattered company knowledge — documents, SOPs, policies, FAQs, tables, and structured reference material — into a private assistant that gives your team fast, source-grounded answers.
Tell us about your setup and we'll confirm fit, scope, and pricing.