CogneraGet in touch

How an installation is put together.

Cognera is installed onto a machine rather than signed up for, so the setup is a real process with real decisions in it. These are the chapters of that process, in the order they happen.

None of this requires you to do it yourself — it is documented because you should know what is being done to your own equipment.

01
First

Securing the machine.

A private AI stack is only private if the box it runs on is. This comes before any service is switched on.

A

Network boundary

Services bind to the local machine rather than the open network. What reaches the outside world does so through a single reviewed tunnel, not through a port opened on your router.

B

Access control

Anything published externally sits behind an identity gate, so reaching it requires being on a list — not merely knowing the address.

C

Secrets

API keys and tokens live in files readable only by the account that needs them, never in the project itself and never in a backup archive.

Service binding
Local interface
Inbound ports
None opened
External access
Tunnel + identity gate
Credentials
Owner-readable only
Fig. 1
Fig. 1 — Request path from visitor to local service. Diagram to be placed.
02
Then

Activating the services.

Each surface is brought up on its own and confirmed working before the next one is added, so a fault has only one possible cause.

  1. 1

    Model runtime

    The local model runtime is installed and the models you will actually use are pulled down and kept resident, so the first request of the day is not a cold start.

  2. 2

    Knowledge base

    Your documents are collected, converted where needed, and indexed. This is the step that decides how well anything answers, so it is worth doing properly.

  3. 3

    Service surfaces

    Website Studio, Media Studio, and the Voice Agent are enabled according to your plan, each verified against the running model before moving on.

  4. 4

    Restart survival

    Everything is registered to come back automatically after a reboot or a power cut. An installation that needs a person to restart it is not finished.

03
Ongoing

Keeping the knowledge base current.

The one piece of maintenance that genuinely matters. Everything the agent says comes from here.

Adding material is a matter of putting files in the knowledge folder and re-running the indexer. The index is rebuilt locally and the service picks it up on restart.

The indexer reads Markdown, plain text, PDF, and Word files. Other formats — including source code and spreadsheets — need converting to one of those first, or they are silently skipped.

Accepted
.md · .txt · .pdf · .docx
Skipped silently
Everything else
After indexing
Restart the service
Runs on
Your machine
Fig. 2
Fig. 2 — Knowledge folder and the indexer output. Screenshot to be placed.
04
Reference

What each plan turns on.

Plans differ in which surfaces are activated, not in how well they run. There is no throttled tier.

Studio
Website Studiosite generation and grounded concierge
Premier
Full stackadds Media Studio and Voice Agent
À la carte
Selected surfacesplus security and activation work
All plans
Unmeteredno per-use billing on your own hardware