coiai Logo

On-premise AI development

Turn internal knowledge into AI people can use.

Private AI needs more than a local model: it needs access controls and a workable operating model. We build local LLM and RAG environments from workflow discovery through validation, training, and everyday use.

Last updated: / Reviewed by: Akira Hattori(Representative Director & CEO / CTO)

Chat interface of our LLM Link application
Example of our LLM Link application. Models and features are selected for each deployment.

At a glance

On-premise AI runs a generative AI model (a large language model) on your own servers inside your network, so internal documents and business data are used without being sent to an external AI service. coiai Inc. delivers this with LLM Link, its own AI application, covering workflow discovery, AI server selection, retrieval-augmented generation (RAG) with user and group permissions, validation, staff training, and ongoing support.

Who it is for
Organizations that cannot send confidential documents to external AI services. A standard configuration is sized for day-to-day use by about 50 people.
Scope
Workflow discovery, AI server selection, LLM Link deployment, RAG with user and group permissions, load and access validation, training, and remote support.
Indicative pricing (excl. tax)
Software JPY 650,000 (one-time, unlimited accounts), setup and training JPY 700,000, support JPY 130,000 per year, AI server approx. JPY 1,000,000.
Subsidy
LLM Link is an eligible IT tool under Japan's Digitalization and AI Adoption Subsidy. As a registered IT implementation support provider, we assist with the application.
Supported documents
PDF, Word, Excel, text, Markdown, and images. CSV and Excel data can also be aggregated, charted, and summarized in AI reports.
Track record
Deployed for a company in Japan (name withheld), including hardware load tests, automatic startup and restart, backups, recovery after power restoration, and a training curriculum.
Service area
Japan. Support is delivered remotely; on-site work is quoted separately.

01 / PRIVATE AI

Start with a problem your team recognizes.

Start with the information, people, and workflows involved. A department’s documents or recurring internal questions can provide a concrete starting point for evaluation.

Sensitive documents cannot leave

Contracts, technical records, and internal policies may be restricted from external AI services. We map the data and communication constraints before selecting a local deployment.

Finding knowledge takes too long

Manuals and past responses are scattered, so staff repeatedly ask the same experts. We design document retrieval with answers that users can check against source material.

Adoption needs more than hardware

Document updates, access management, and staff education need owners and procedures. We shape the environment around the people who will operate and use it.

02 / PRIVATE AI

Connect search, summaries, and drafts to your knowledge.

We define the scope around your workflows and operational requirements.

Questions about policies and procedures

Help staff find relevant internal rules and application procedures. Document versions and update dates matter; users should check the original material before acting on an answer.

Technical and quality knowledge

Provide an entry point to incident reports, inspection records, and work instructions. Evaluate retrieval using the terminology and questions staff actually use.

Summaries and writing assistance

Help organize long documents and draft internal explanations. Training covers human review of accuracy and confidentiality before generated text is used.

These are potential uses. Outcomes must be evaluated against the actual documents, workflows, and usage patterns.

03 / PRIVATE AI

How a question becomes an answer inside your environment.

Private AI design is not only about where the model runs. It defines who may search which documents and how users can verify the basis of an answer.

Example within an internal network: user → access and retrieval → local LLM → answer

  1. 01

    Authenticate

    Identify the user and their groups when they access the application in a browser.

  2. 02

    Retrieve within permissions

    Index approved documents and filter retrieval to what this user can access.

  3. 03

    Generate locally

    A local language model uses the retrieved context to help produce an answer.

  4. 04

    Verify and maintain

    Check source documents and maintain conversation history, users, and document updates.

RAG retrieves documents as context at answer time; uploading documents does not retrain the model. Routine traffic is reviewed separately from model downloads, updates, and remote support when defining isolated operation.

04 / PRIVATE AI

Usable for employees. Manageable for administrators.

Manage document and user groups, and apply permissions to retrieval, answers, document lists, and source downloads. Validate behavior using the roles expected in your organization.

Document ingestion and management
Document ingestion and management

Validate ingestion and retrieval for PDF, Word, Excel, text, Markdown, and images. Complex tables, scan quality, and visual content affect extraction accuracy.

Users and groups
Users and groups

Add users and assign groups in the management interface. Administrators have broad access, so ownership and joiner, mover, and leaver procedures are part of the operating model.

05 / PRIVATE AI

Analyse internal data in the same AI environment.

LLM Link also aggregates and visualizes CSV and Excel data. Select files and describe what you need: AI reads column names and types to design metrics, aggregations, and charts, and the server performs the calculations. Report summaries draw on finalized figures and documents the user selects, and are reviewed before sharing.

Analysis: choose files and ask
Analysis: choose files and ask

Select CSV or Excel files such as sales lists, payroll, or contract registers and describe the view you need. Saved transformations and metrics can be reused on next month's data.

AI reports with cited sources
AI reports with cited sources

Draft summaries from finalized figures and selected internal documents, with the sources listed. Reports can be scheduled daily, weekly, or monthly.

Screens show fictitious demo data.

06 / PRIVATE AI

Choosing on-premise, cloud, or hybrid AI

Not every workload belongs on premises. Placement should follow confidentiality, update needs, performance, and the operating model for each use case.

Choosing on-premise, cloud, or hybrid AI
ConsiderationCloud AIOn-premise AIHybrid
Data locationSent to and processed by an external serviceProcessed inside the organization or designated siteDestination separated by sensitivity
Best fitGeneral information and fast access to newer modelsConfidential documents, internal policies, proprietary knowledgeOrganizations with both general and sensitive work
Performance and scaleUses the provider's broad compute capacityPredictable within owned infrastructureAllocates performance and control by workload
Updates and operationsUpdates are primarily provider-managedUpdated and monitored under internal policyRequires rules and connection management for both
Cost profileTypically ongoing usage-based chargesUp-front hardware and delivery plus supportBalances investment and usage fees by workload

A general comparison; contracts, models, and infrastructure vary. Local deployments have hardware and operational constraints, and do not automatically match cloud model quality or speed.

07 / PRIVATE AI

Choose hardware and models against real workloads.

We do not force a predetermined configuration. We propose a fit-for-purpose environment after reviewing use cases, target data, internal policies, and expected adoption.

We define the scope around your workflows and operational requirements.

Concurrent work matters more than account count

Registered users are not simultaneous requests. Document volume, prompt and answer length, and model memory requirements inform GPU, memory, and storage selection.

Measure quality and latency separately

Prepare representative questions and expected evidence. Evaluate missed retrieval, grounding, time to first response, and completion time separately, recording model, hardware, and concurrency conditions.

Check existing infrastructure and integration

Reusing a server depends on its specifications. SSO, internal wikis, and file servers require individual evaluation of interfaces, access mapping, and update frequency.

08 / PRIVATE AI

A deployed internal AI environment, with operational support.

Anonymous engagement / deployed

What we delivered

We deployed an AI environment for a company in Japan using our LLM Link application, including authentication, group-aware RAG, document management, and separate user conversation histories.

Verification and operational preparation

Work included hardware load tests, automatic startup and restart, daily backups with 14 generations retained, and recovery after power restoration. We also built 30 automated tests covering authentication, document permissions, retrieval, and conversation isolation.

Measured on the actual hardware

Sized for day-to-day use by about 50 people, the system was tested with up to 24 simultaneous requests. With 8 simultaneous users, every response began streaming without a wait. A 10-session training curriculum covers generative AI basics through RAG and in-house development.

  • Hardware selection
  • Permission-aware RAG
  • Load test up to 24 concurrent requests
  • 30 automated tests
  • Backup and recovery
  • 10-session training

The client is not named. Load-test figures come from our own tests on specific hardware with a standard model, responses fixed at 120 tokens, and a local network; actual performance varies with configuration, model, response length, and concurrent use. Time savings and adoption rates have not been measured and are not presented as outcomes.

09 / PRIVATE AI

Validate a focused scope before production.

When a PoC is appropriate, agree on workflows, evaluation questions, success criteria, and scope first. Results should support a decision to proceed, investigate further, or stop.

  1. Workplace and workflow discovery

    We examine work, confidential information, users, documents, and the existing environment, then define purpose and evaluation.

    Outputs and acceptance: Candidate uses, target data, assumptions, and indicative estimate
  2. AI training and architecture

    Once users and administrators understand AI behavior, we design models, hardware, permissions, networking, and operations.

    Outputs and acceptance: Architecture, permission policy, evaluation plan, and confirmed estimate
  3. Environment, RAG, and validation

    We implement authentication, ingestion, retrieval, answers, history, and administration, then validate quality and performance with real content.

    Outputs and acceptance: Working environment, test results, and tuning record
  4. Training, production, and improvement

    We train users, hand over administration, and improve supported workflows based on workplace feedback.

    Outputs and acceptance: User and operating guides and improvement plan

Timing depends on document readiness, procurement, integrations, and internal reviews. The proposal defines scope and schedule for each stage.

10 / PRIVATE AI

Plan for day-to-day ownership before launch.

We define the scope around your workflows and operational requirements.

Documents, permissions, and history

Assign owners for document updates, re-indexing checks, access changes, and log retention. Document the procedures so the environment remains maintainable after deployment.

Backup and incident response

Define backup scope, frequency, retention, copy destinations, and restoration checks. Agree monitoring, escalation, support hours, and maintenance responsibilities.

Model updates and user education

Recheck quality and permissions against representative questions after updates. Teach limitations, source verification, and appropriate inputs; use staff feedback to prioritize improvements.

11 / PRIVATE AI

Price list

Pricing for a standard deployment with LLM Link. Software, implementation, support, and hardware are priced separately. The software is sold at list price without discounts.

Price list
ItemPrice (excl. tax)Price (incl. 10% tax)Scope
LLM Link softwareJPY 650,000 (one-time)JPY 715,000One company, one environment, unlimited user accounts. Includes permission-aware document-search chat, data import and transformation, metrics, dashboards, AI-assisted analysis design, AI reports, and permissions
Setup, manuals, and trainingJPY 700,000 per deploymentJPY 770,000Installation and permissions, import of existing data with saved transformations, initial AI configuration, training materials and two sessions, operations manual
SupportJPY 130,000 per yearJPY 143,000Enquiries (weekdays 10:00–18:00), defect investigation and fixes, update installation. Delivered remotely
AI server (hardware)Quoted separately (approx. JPY 1,000,000)—Reference standard configuration for day-to-day use by an organization of about 50 people. Selected to match usage and concurrency

Prices as of 9 October 2026. Discovery or PoC work, integrations, custom development, on-site work, and travel are not included and are quoted separately against agreed scope.

12 / PRIVATE AI

Why the price does not grow with headcount.

01

AI runs on your hardware

Processing happens on your AI server, so adding users does not add cloud charges. Concurrent capacity depends on the hardware configuration, not on the number of accounts.

02

Development cost shared across customers

The price assumes shared product development costs across multiple deployments, and sits at a similar level to one-time licences for on-premise BI products in Japan.

03

Itemized costs

Software, implementation, support, and hardware are listed separately. Implementation and support are priced from hourly rates and estimated hours.

13 / PRIVATE AI

How it differs from other AI services

LLM Link focuses on searching internal documents and analysing internal data. The main differences are the pricing model and where data is processed.

How it differs from other AI services
ItemLLM LinkMicrosoft 365 CopilotPower BI + Copilot
Pricing modelOne-time software licence plus annual support. Unlimited accountsJPY 3,148 per user per month (annual). Requires an eligible Microsoft 365 licencePower BI Pro JPY 2,098 per user per month (annual). Copilot requires a Fabric capacity (F2 or above)
Where data is processedYour AI server, inside your companyMicrosoft cloudMicrosoft cloud
AI usage and costNo charge per use. Capacity depends on hardwarePer-user subscriptionConsumes Fabric capacity units
StrengthsInternal document search, data analysis, and reportsBroad productivity across Word, Excel, Teams, and moreLarge-scale BI and data platforms

Third-party prices are published list prices (excl. tax) checked on 9 October 2026. Features and terms differ; confirm current prices with each vendor.

14 / PRIVATE AI

Three-year cost comparison (Microsoft 365 Copilot)

LLM Link costs the same regardless of headcount. At 30 users or more, its three-year total is lower than Microsoft 365 Copilot.

Three-year cost comparison (Microsoft 365 Copilot)
UsersLLM Link (3 years)Microsoft 365 Copilot (3 years)Difference
20JPY 2,740,000JPY 2,266,560Copilot lower by JPY 473,440
30JPY 2,740,000JPY 3,399,840LLM Link lower by JPY 659,840
50JPY 2,740,000JPY 5,666,400LLM Link lower by JPY 2,926,400

All figures exclude tax. LLM Link totals software JPY 650,000, setup and training JPY 700,000, support JPY 130,000 × 3 years, and an AI server of approx. JPY 1,000,000. Microsoft 365 Copilot is JPY 3,148 per user per month (annual) × users × 36 months, excluding the required Microsoft 365 licence. Hardware cost varies by configuration, and heavier concurrent use may require a different configuration.

15 / PRIVATE AI

FAQ

What is on-premise AI?

It means running a generative AI model on servers inside your own network. Questions and internal documents are processed without being sent to an external AI service, which suits confidential work, but your organization takes on hardware, model updates, and operations.

How much does it cost?

A standard LLM Link deployment is software JPY 650,000 (one-time), setup and training JPY 700,000, support JPY 130,000 per year, and an AI server of approx. JPY 1,000,000, all excluding tax. There is no per-account charge. Discovery, PoC, and integrations are quoted separately.

Does it run on existing servers?

We assess whether existing equipment can be used and recommend an architecture for the intended use and adoption level. We can also help select new hardware when needed.

Can it work fully offline?

Routine use can be designed to stay within your environment. Full isolation also requires review of model transfer, updates, software dependencies, and support procedures.

Does RAG guarantee correct answers?

No. Document quality, retrieval, and model interpretation can all introduce errors. We evaluate real questions and define how to handle uncertainty and human verification.

Can access differ between employees?

User and document groups control retrieval, answers, lists, and source downloads. Validation covers expected roles, operational settings, and administrator privileges.

How are post-deployment updates handled?

Model and software updates, new documents, and configuration changes are handled within an agreed support scope. Update procedures for closed networks are designed separately.

Can it be used alongside cloud AI?

Yes. We propose hybrid configurations — on-premise for confidential data, cloud AI for general tasks.

What determines the cost?

Cost varies with the intended use, target data, existing environment, integrations, and post-launch support. We review these conditions and propose an appropriately sized environment and estimate.

Can we enquire without an AI specialist?

Yes. We identify the relevant workflows and who can own equipment, documents, and access, then include appropriate education and support in the proposal.

Does the price increase with more users?

No. LLM Link has unlimited user accounts. Concurrent AI capacity depends on the hardware, so the AI server is sized to your usage.

Does support require on-site visits?

Support, including update installation, is delivered remotely. Any on-site work is quoted separately.

Can subsidies be used?

Yes. LLM Link is registered as an eligible IT tool under Japan's Digitalization and AI Adoption Subsidy for SMEs, and coiai is a registered IT implementation support provider that assists with the application. Eligible costs, subsidy rates, and caps depend on the application category and your business, and approval is subject to review. Costs contracted or paid before the grant decision are not eligible, so please contact us before signing.

Explore the next questions

Connect business systems and AI

Business systems organize operational data; AI helps people use it. We can scope their roles and any necessary integration together.

Explore core systems →

LET’S TALK

You do not need a finished brief.

Tell us what is difficult today and what you want to make possible. We can start by clarifying the scope, constraints, and practical next steps together.

Enquiry → review and reply → discovery conversation → proposed next steps. Research and development costs are proposed after clarifying the scope.