Morpheus

The most useful thing in the universe — which is most certainly not a towel — is an assistant that can give you the information you need exactly when you need it. Morpheus does precisely that: manages your servers, learns from your past conversations, picks the right tool from 30+ AI tools, and runs all your operations from a single chat window.

What is Morpheus?

Morpheus is VeriTeknik Ops Hub's AI assistant. Through Hub Chat, you can use natural language to:

• Manage your servers — service status, log inspection, backup, SSH command execution
• Domain operations — lookup, registration, transfer, renewal, DNS
• Track your invoices — balance, payments, invoice details, payment links
• Pay invoices — say "Pay my February invoice from balance" and Morpheus finds it, confirms/applies payment, and reports the result. For saved cards, "Show my saved cards" is enough.
• Create and track support tickets
• Schedule meetings — with Google Calendar integration

Like the "Don't Panic" inscription on the cover of the Hitchhiker's Guide, Morpheus is always calm and helpful. And it connects to 13 external systems to execute operations on your behalf.

Getting Started

To access Hub Chat, click Morpheus in the left menu or go directly to /hub/chat.

On the welcome screen you'll see four quick-start cards:

Card	What It Does
Servers & Infrastructure	Your VPS instances, server status, contracts
Domain Operations	Domain lookup, registration, transfer
Server Management	SSH service control, logs, backup
Billing & Support	Invoices, payments, support tickets

Click a card or just type — Morpheus will understand what you need.

Model Selection

Deep Thought might spend seven and a half million years choosing a model; you can open the model selector at the top left. It lists models available to your account, the provider receiving your data, and selling prices for paid models.

Option	Where it runs	Pricing
ikigAI (morpheus-general)	VeriTeknik data center	Free local option
Evren (deepseek-v4.1-flash)	External provider through our gateway	Default for web Hub; current free or paid status appears in the selector
Claude	Anthropic infrastructure	Token prices for models available to your account appear in the selector

Check the data location notice before sending content to an external provider. Availability is model specific; the selector shows the versions your account can use.

How pricing works

Input and output prices in the selector are per million tokens and include the selling margin. For a model with a long-context tier, a second line shows prices above the threshold; when a prompt exceeds it, all relevant tokens use that tier. One message can involve several model calls when tools are used; each call is counted separately. If a fallback serves a call, you pay no more than the selected model would charge for the same usage. The total is deducted once per turn from your TRY wallet; a positive paid turn costs at least TRY 0.01. Failed turns show Not charged; a turn waiting for approval or verification may charge for usage already incurred.

Repeated content and caching

When a provider reports cache usage, regular input, the first write, and later reads are priced separately. A typical Anthropic five-minute cache write costs 1.25 times regular input and a read costs one tenth; the verified model tariff takes precedence. Early turns pay the writing premium; savings appear in multi-step tasks and follow-up turns while the prefix remains cached. This release adds no new caching markers to chat requests and does not promise a discount on every message.

Pack your towel and check your balance

Your wallet is checked before a paid model starts. If funds are insufficient, top up or choose the free ikigAI option.

The Thought Stream and the "Think" Switch

Deep Thought thought for seven and a half million years and never showed anyone what it was thinking. Morpheus is less mysterious: on the local model (ikigAI) it thinks before it answers, and it does not hide that.

• While it thinks, a Thinking label shimmers above the answer and the last lines of the thought stream in live.
• When it is done, the line folds into Thought · 1.8 s; click it to read the whole thought.
• If you would rather it did not, turn off the Think switch in the chat header, next to the model picker. Your choice is remembered in your browser, and that chat's answers come back a little faster.

The switch appears only on the local model; cloud models do not use thinking anyway.

A thought is not an answer

The thought stream is the model talking to itself - thinking out loud. The answer is in the answer; the stream only shows how it got there. On a long installation it is remarkably useful for seeing exactly where things got stuck.

DevOps Agent

Morpheus isn't just for answering questions — it can directly manage your servers. It uses Ansible playbooks to perform OS-aware operations. Like a galactic engineer, but without the Vogon bureaucracy.

Connection Setup

1. Go to VPS Servers in the left menu
2. Select the server you want to manage
3. Click the Morpheus tab
4. Turn on the Morpheus Agent switch (if you have not accepted the CogMem-AI addendum yet, you accept it first)

If you turned Morpheus on when ordering the server, the access is already there and the connection sets itself up. If you did not (that is the default), nothing of Morpheus exists on the server; the portal gives you a setup (bootstrap) command. Connect to the server as root (over SSH or the console) and run it once; the command is valid for 10 minutes, and the tab switches to "Morpheus Active" on its own when the setup completes.

Right From the Start: Enable Morpheus When You Create a VPS

You don't have to wait for your server to exist before introducing it to Morpheus. The new-VPS purchase flow now has a dedicated Morpheus step, tucked between the hostname step and the final confirmation. There you can sort everything out up front:

• Read, in a few lines, what Morpheus and its CogMem-AI cognitive memory actually do — so you know what you're saying "yes" to before you commit.
• Flip the "Enable Morpheus at setup" toggle. It's entirely up to you and off by default (opt-in) — nobody switches it on behind your back. If you leave it off, no Morpheus user, key or permission is created on the server.
• To enable it, accept the CogMem-AI Data-Processing Addendum — a consent checkbox with a link to the full text. We don't expect you to tick the box blind; the link is right there, read as much of it as you like.

When your server is ready, Morpheus is ready too — no separate trip to a tab to wire up the connection.

No rush — you can always enable it later

Enabling Morpheus at setup is completely optional. Want to skip it for now? Perfectly fine - you can switch it on any time from the Morpheus tab on your server's page. You then run a setup command once on the server as root (see Connection Setup). Your call, your timing.

What does the CogMem-AI consent actually mean?

Don't panic — the only thing processed here is anonymized operational data; it's about how your server behaves, not who you are. The process is KVKK-compliant, and if you change your mind you can withdraw consent at any time. The babel fish comes out of your ear whenever you want it to.

What Can You Do?

Once connected, you can say things like:

• "Check the disk usage on my server"
• "Restart nginx"
• "Show the last 100 lines of error logs"
• "Apply security updates"
• "Take a database backup"

Ansible Playbook Integration

Morpheus uses VeriTeknik's DevOps playbook library for structured operations:

• OS updates — Ubuntu, Debian, CentOS, Rocky Linux — correct commands auto-selected per distribution
• Security hardening — SSH hardening, unnecessary service shutdown, firewall rules
• Service management — start/stop/restart, log inspection, configuration checks
• Backups — database dumps, filesystem snapshots
• Disk cleanup — log rotation, temporary file cleanup

How Does It Work?

You: "Check the disk usage on my server"
  ↓
Morpheus → Selects appropriate Ansible playbook → Asks your approval
  ↓
You approve → Playbook runs → Results reported
  ↓
"87% usage on /. /var/log cleanup recommended. Shall I proceed?"

Security — Autonomous but Controlled

By default, write operations (service restarts, file deletion, updates) require a verification code. Read-only commands (disk status, log reading) run without approval. Every operation is written to a PCI-DSS compliant audit log.

How much gets asked is your call: the Yetki seviyesi (autonomy level) on Sunucular (Servers) > the server > Morpheus has four settings - fully autonomous, safe automatic, ask every time (the default), observe only. Destructive work (mass deletion, disk formatting, reinstall) runs at no level, neither from the chat nor from a connected app. To allow one batch without lowering the level, enter your code on the Komut kilidi (command lock) card on the same tab. Only the company owner or an admin can change the level, and every change is written to the audit log together with what it was before.

Reinstall Your Server: Morpheus Comes Back If It Is On

Reinstalling a server from scratch is sometimes unavoidable: a clean slate, a different operating system, or simply the urge to wipe everything and start over.

A reinstall looks at whether Morpheus is on for that server at that moment:

• On: your SSH keys and Morpheus access are restored automatically once the install finishes. You do nothing; the server comes back up, and Morpheus comes back with it.
• Off: only your SSH keys are restored. The reinstalled server has no Morpheus user, key or permission.

The decision comes from the server's recorded state, not from the request: a reinstall never brings Morpheus in unless you turned it on. For Morpheus to come back, your CogMem-AI addendum must also still be in force.

Don't Panic: a connection that is on is not lost

If Morpheus was on when you reinstalled, there is no need to enable it again or run the setup command by hand. Your server reconnects to Morpheus reliably, like a good towel that always knows where it is.

Removing Morpheus access from older servers

On some servers created before the rule that Morpheus is set up only when you turn it on was fixed, a morpheus user, a shared SSH key and passwordless sudo exist even though Morpheus was switched off. You can ask us to remove it or remove it yourself; the steps and the check are on Data Processing Agreement > Removing Morpheus access.

Morpheus's Computer

The terminal panel to the right of the chat is now more than a terminal: it is Morpheus's computer. A screen you can look over its shoulder at while it works.

• At the top, one sentence says what Morpheus is doing right now: thinking, using a tool, running a command in the terminal, waiting for your approval.
• In the middle, you see that step's own screen: the thought, the tool result, the command and its output, the blast radius of an action awaiting approval.
• At the bottom there is a slider. Step back through every step of the turn to see what happened at that moment, then hit Live to return to now. Clicking a chat block opens the panel straight at that step.

Above the message box there is also a one-line task strip: a small preview, which step Morpheus is on, and how many steps are done. Click it and the full working plan opens. When there is no plan, the strip does not invent steps - it counts the tools that ran.

Rewinding does not undo anything

The slider is a recorder, not a time machine: you look at the past, you do not change it. Morpheus keeps working while you are ten steps back; hit Live and you find it exactly where it got to. You can look behind you without putting your towel down.

Multi-Step Task Card

Some operations don't finish in a single message — VPS order flows, domain transfers, contract + onboarding — these involve several controlled steps. Morpheus now runs these flows on a deterministic task engine:

• Each step begins with a gate (precondition check) — is balance sufficient, is a card saved, is the contract signed?
• If a condition is missing, Morpheus tells you what's missing and points you to the right screen.
• Once you resolve the missing piece, you don't need to say "continue" — Morpheus returns to the flow automatically.
• Task state is shown live as a TaskCard in the chat window: which step you're on, what's pending, what's left.

Why the task card matters

On multi-step operations you never have to ask "where were we?" The task engine doesn't lose steps, doesn't run them twice, and preserves state even if you switch tabs. No Vogon triplicate forms.

The Card No Longer Repeats You

The task card used to print the message you had written as its own heading, and it stayed on screen after the turn had ended. Your own sentence came back at you looking like a command.

Now the card appears only while the turn is running, and its heading says what is actually happening: Working while it works, Approval needed or Verification needed when it wants something from you. When the turn finishes the card disappears - the work is already in the answer. Cards in the conversation history follow the same rule: Task completed, Left unfinished.

The card's category and step labels are written in plain Turkish and English now, instead of raw codes. And one honesty fix: a command that failed on the first attempt and succeeded on the second no longer fails the whole task. The verdict follows the final state, and the recovered attempts are noted in an information line under the answer.

Memory System — Cognitive Memory Architecture (CogMem)

Morpheus isn't a one-shot chatbot — it learns from every conversation, remembers what matters, and naturally forgets what doesn't. Just like human memory — but unlike Marvin, without getting depressed about it.

TUBITAK 1501 R&D Project

CogMem — Cognitive Memory Architecture is being developed under the TUBITAK 1501 Industrial R&D Projects program.

Memory Rings

Morpheus's memory consists of six concentric rings. From inner to outer, each ring represents more permanent and more selective information:

Ring	What It Stores	Example	Behavior
Fresh	Temporary info from recent conversations	"We just restarted nginx"	Naturally fades after 30 days
Long-term	Proven permanent information	"My name is Cem, CEO of VeriTeknik"	Auto-injected every conversation
Habits	Recurring behavioral patterns	"Always takes backup before deploy"	Injected on relevant topics
Procedures	Workflows, procedures	"Domain order is an 8-step process"	Injected on relevant topics
Shocks	Critical events, never-forget items	"Cascade failure occurred, root cause: disk"	Auto-injected every conversation
Dos & Don'ts	Prohibitions and rules	"No restarts after 10:00 PM"	Auto-injected every conversation

BIOS Layer

Beyond the memory rings, there's an immutable BIOS layer. PCI-DSS rules, ISO 27001 controls, customer SLA requirements — these are automatically injected into every conversation and can never be modified.

Example BIOS rules:

• "Root access is restricted on PCI-DSS scoped servers"
• "Warn when SSL certificate expires within 14 days"
• "Customer SLA: first response < 15 minutes"

Reinforcement Lifecycle

Memories naturally fade — just like Ebbinghaus's forgetting curve. But memories used in successful conversations are reinforced:

• Morpheus uses a memory and the conversation succeeds
• recall_count and success_score increase
• Memories exceeding the threshold are promoted to a higher ring
• Unused memories naturally fade (decay gradient: 0.9/30 days)

Result: What matters stays, what doesn't naturally disappears. No manual cleanup needed.

Memory Management

To view, edit, or delete what Morpheus knows about you:

1. Click the Memory link in the top-right of Hub Chat
2. Or go to Settings > Memory tab

There you can:

• View all memory rings and BIOS rules
• Edit or delete any memory (except BIOS)
• Click Analyze to trigger memory extraction from today's conversations
• GDPR/KVKK right: Delete all your memories at once

Automatic Learning (Nightly Cron)

Every night at 02:00, Morpheus analyzes the day's conversations:

• Saves valuable information to the appropriate memory ring
• Updates reinforcement scores
• Promotes memories that exceed thresholds
• Applies the decay gradient — unused fresh memories fade

The same nightly pass now also consolidates. It used to look only at reinforced records; where reinforcement never happened, repetitive and occasionally contradictory records piled up. Now every long-term record older than a day is a candidate for consolidation, while frequently recalled live records are preserved. The same rule applies to procedures and habits: three separate records of one procedure collapse into a single record with its steps intact, and two different habits are never generalised into one sentence.

Relevant Memory Arrives With the Task

Learning something and then leaving yourself to remember it next time is a forgivable human flaw, and an unforgivable assistant one. Now, when a server task begins, what was learned before about that server and that kind of work - procedures, facts, habits - is put in front of Morpheus automatically. Notes belonging to a different server are filtered out. The strongest recall is shown to you too, as a from memory card at the start of the task, so you can see what Morpheus is remembering.

Memory Hygiene

Memory does not only accumulate, it also cleans up after itself:

• A deleted server leaves no notes behind. When you delete a server, the notes about it (IP, operating system, installations) are replaced by a single record saying the server was deleted on that date and the old notes no longer apply. A released IP can reach another customer quickly, so this is not politeness, it is necessity. The deletion's own notification, and shared notes that also mention a server still standing, are left in place.
• An unfinished task leaves a note for the next attempt. If a task crashes with a system error, Morpheus leaves a short note: what was asked, which server, how many steps ran, check the current state first. It is in front of it in the next conversation, so the second attempt does not start from zero.
• Sentences containing the word "password" are no longer censored. A reminder like "the DB password is in /root/wp-credentials" used to be scrubbed purely because it contained the word, losing its meaning with it. The cleaner now removes only values that genuinely look like secrets; where a password lives stays readable. Real passwords still cannot enter memory.

Morpheus knows your e-mail address now

Alongside your name and company, the identity summary now carries your account e-mail. When a step needs a contact address (a Let's Encrypt certificate registration, say), Morpheus uses the address on your account instead of stopping to ask. It also records preferences you state out loud - "use this address for certificates" - as habits, without asking.

Channels

Morpheus is accessible from multiple channels, not just Hub Chat — like the hitchhiker's towel, always with you wherever you go:

Channel	Model	Status	Description
Hub Chat	Evren / ikigAI / Claude	Active	Full-featured: tool use, memory, SSH
Telegram	ikigAI	Active	Notifications, quick queries, 2FA commands
Phone	Evren (deepseek-v4-flash) + Google STT + TTS	Beta	Voice assistant - via Issabel PBX
Website	Evren	Active	On the service pages, in the top menu and at /chat; answers without signing in too
Slack	—	Planned	Team notifications

Morpheus on the Website

Morpheus waits for you on veriteknik.com's service and solution pages, behind the meeting button in the top menu, and at /chat. On each page it opens with that page's subject: on the DevOps page it asks about your deployment process, on the cybersecurity page about your compliance needs.

• If you are not signed in, it answers questions about our services and connects you with the right team for a meeting. It cannot reach your account, servers or invoices.
• If you are signed in, it recognizes you: it does not ask for your name and e-mail again, and books the meeting for you directly. To have work done on your servers, use the chat in the panel; the website window does not do that.
• A conversation belongs only to the browser tab you opened it in. It cannot be continued from another tab or through someone else's link.

PCI-DSS Compliance

Morpheus is designed to meet PCI-DSS 4.0 requirements:

• Local AI model — with ikigAI, your data never leaves our data center
• Audit trail — all memory operations and commands are logged
• Tenant isolation — each company's data is completely separate
• Right to erasure — delete all your data under GDPR/KVKK
• Encrypted communication — all connections are encrypted
• Immutable audit trail — Elasticsearch write-only, undeletable logging

Model Selection and PCI-DSS

When using ikigAI you'll see a green PCI-DSS ✓ badge. When Claude models are selected, a red PCI-DSS ✗ badge warns you — data is sent to Anthropic servers with those models.