A local AI assistant runs on a computer your business controls. This pilot explores one practical use for your team, using a small set of approved company documents, before you decide whether a wider rollout is worthwhile.
$3,500USD · one-time service fee
Hardware and any agreed paid software licenses are separate. No required monthly Fucira fee. We confirm hardware suitability and the scope before you commit; a paid roadmap is not required for this pilot.
Typically delivered over 2–3 weeks after equipment, approved files and IT access are ready. This is a limited pilot for internal staff use. It helps establish what works on your tasks and hardware.
Verified non-profits receive Fucira’s 35% discount on eligible service fees. Hardware and provider fees are excluded.
A defined starting point for one department. The price covers the implementation work below, with hardware quoted separately.
On-site visits or travel, scanning and OCR, substantial file cleanup, live connections to shared drives or business apps, automatic file synchronization, multiple permission groups, remote staff access, transcription, custom model training and actions that change business records. Hardware replacement, high availability and 24/7 support are also outside the pilot.
The library is a snapshot of the files you approve. We show your administrator how to refresh it manually. New or changed files are not included automatically.
Your nominated owner and IT contact work with Fucira through four stages. Equipment delivery and internal approvals can affect the schedule.
Step 1
Review your task, sample files, hardware and network with your nominated owner. Agree the evaluation targets, approved users, data handling and fixed scope before work starts. If it does not fit the pilot, we explain why before you commit.
Step 2
Your team supplies approved files, a suitable machine, backup storage and authorized IT access. We install and configure the local model, document search, accounts and network restrictions through an agreed remote setup session.
Step 3
Run the agreed questions, verify source references, test access restrictions and recovery, and repeat chat and new-document processing with external access blocked. Review recorded network checks separately from answer quality.
Step 4
Train the team, provide the configuration and test record, and start the 30-day support period. At the end, review usefulness, limitations and whether to maintain, expand or stop using the pilot.
If the agreed checks do not pass, we document the gap and review corrections within the agreed scope before handoff. Any additional equipment or broader work needs a separate written agreement.
The main benefit is control over where the agreed AI workflow processes information. It reduces a specific kind of data sharing; it does not remove every security risk.
The model and supporting software are made by other organizations. Local hosting removes the need to send the pilot’s content to a third-party AI processor; it does not eliminate software suppliers, license obligations or security updates. Some hosted business AI services also offer contractual data protections. The difference here is where processing happens.
We check document reading and search as well as the chat model, because a local chat screen can still connect to outside services. Installation and maintenance can involve downloads. The handover records allowed connections, storage locations, retention settings and the checks performed.
Encryption helps protect stored data on a lost or stolen drive; an unlocked or compromised computer can still expose it. Authorized users can copy answers or export files. Your team remains responsible for device security, staff access and deciding what information belongs in the pilot.
Fucira may see approved documents during setup or support. Access is limited to the agreed work, remote access is enabled only for approved sessions, and temporary working copies are removed at handoff unless you agree another retention period. Support reports use operational details rather than document or chat contents wherever possible.
A LAN-only installation is not automatically air-gapped or a compliance certification. The standard pilot does not include patient records, payment-card data, export-controlled material or other data requiring a separate regulated deployment review. AI answers still need human review, including checking their sources.
Running a downloaded model locally does not require a hosted AI fee for each prompt. Keeping a useful business system running still takes equipment, electricity and maintenance.
No ongoing Fucira service fee
After the included 30-day support period, your administrator can run the system using the handover guide. Your business covers power, backup storage, hardware repairs and replacement, and any separately agreed software licenses. Your team handles updates, file refreshes and troubleshooting. Later Fucira help is quoted separately.
$499/month · one established local workflow
Pays for Fucira’s maintenance and support work: a monthly health and answer-quality review, backup verification, planned security updates and small fixes or library refreshes within the existing scope. Model changes are tested and approved before installation.
Up to two hours of hands-on work per month in total, including reviews and troubleshooting. Support replies within one business day during agreed business hours; no guaranteed resolution time. Hours do not roll over. Extra work needs an agreed price first.
Care has a three-month initial term, then runs month to month with 30 days’ notice to cancel. It is not a model rental or a per-user AI fee. Canceling care does not disable the installed system or remove your documents; your administrator takes over maintenance.
Care starts after handoff if you choose it. During the first 30 days, included launch support covers setup questions and fixes; care covers the scheduled maintenance work. We record the distinction in the quote and do not bill the same work twice. There is no separate care onboarding review for the pilot we just delivered.
For a system with external access blocked, health reports and maintenance happen through approved sessions or customer-provided reports. Continuous remote monitoring is not assumed. Hardware, paid licenses, new integrations, on-site visits and expanded scope are separate.
If you would like to discuss suitability, describe the task, approximate team size and available hardware. Please leave confidential files and personal records out of the initial inquiry.
Ask a question about the pilot
Further reading: Ollama’s local-processing FAQ and Open WebUI’s offline configuration guide explain why local models, document processing and network controls all matter.
