ARCHITECTURE
Six layers, and two rails that run through all of them
Security and pay as you go are not features of one tool. They wrap every layer, so every action is protected and every run is metered. Select a layer or a rail to see what it does.
TOOLS ON THE GO
A tool is a shell plus the modules it needs
Tool shells give every new tool its frame: project, permissions, tasks, notes, chat and reports. Agents plug in the modules the tool needs, and it ships with everything the platform already does. Pick a tool to see what it is made of.
AI WHERE IT HELPS
AI that thinks with your team. Numbers that stay exact.
AI works on ideas, plans and your team’s own knowledge. Metrics come from a deterministic data layer, so a dashboard shows the same value every time you open it.
AI assistance & organization
Content ideasPlatform, format, title and brief for each piece
StrategyChannels and stages built from personas
PlanningCalendars that turn into tasks
BriefingsWhat happened in a project and what is next
PrioritizationImpact and effort, with the team
Your knowledgeAnswers from your notes, tasks and vault
Deterministic data layer
CONTINUOUS AGENTIC DEVELOPMENT
A team of agents keeps building the platform
Users ask for tools. Agents read the requests, write the spec, build, test and document them on top of the framework. A person on the Clevertrek team approves every release.
SC01
Scout
Reads and groups requests
AR02
Architect
Writes the spec
BU03
Builder
Assembles shell and modules
TE04
Tester
Runs tests and edge cases
DO05
Docs
Help and release notes
CT06
Clevertrek team
Approves the release
SH07
Shipper
Publishes it
Each release improves a module, and every tool that uses it improves with it.Open Dev Activity →
SECURITY
Your work history is an asset. We treat it like one.
Clevertrek remembers what happened in your projects: results, decisions, tasks, what worked and what did not. Over time that history becomes one of the most valuable things a company owns, so we protect it in layers.
01Encrypted archiveMemory older than 13 months is encrypted with its own key and moved out of the everyday database.
02The assistant asks firstIt reads the last 30 days on its own. For anything older, it asks you, every time.
03No surprise deletionDeleting the memory of a whole space waits 24 hours, every admin is told, and any of them can stop it.
04A Security adminA person you trust can protect a company space: the admin cannot transfer or delete it without their approval.
The life of a memorySelect a stage
ONE KEY PER SPACE
Deleting a space destroys its key. That makes erasure real.
Each space has its own encryption key, locked by a master key that lives only in the server configuration, with an offline backup. A copy of the database cannot open the archive. When a space’s memory is deleted, its key is destroyed and its packages can no longer be opened by anyone. This technique is known as crypto-shredding.
The archive is write-protected at the storage provider: files can be added, never deleted or replaced. Someone who took over the site could not destroy your history, and neither could we from inside it.
Master keyServer configuration only · offline backupNOT IN DB
↓ locks
Space A keylocked in DB
Space B keylocked in DB
Space C keydestroyed
↓ opens only its own archive
2025-03.pkg
2025-04.pkg
2025-04.pkg
2025-01.pkg
2025-02.pkg
2025-02.pkg
██████.pkg
unreadable
unreadable
PROTECTED STORAGE · WRITE-PROTECTED · ONE PACKAGE PER MONTH
THE SECURITY ADMIN
A second person who protects the space
Every company space has an admin, usually whoever pays for it. The Security admin is a trusted member whose approval is needed to transfer the space, delete it or erase its memory. The admin cannot remove them.
For agencies: make your client the Security admin of their space, and the space and its history cannot be handed to someone else or erased without them.
DELETING THE MEMORY OF A SPACE
1An admin asks for itThey type the exact name of the space. With a Security admin, the other person approves first.
224 hours of graceEvery admin is told in Clevertrek and by email, with a link to cancel.
3A last warningWithin the last hour, everyone is told again.
4The key firstThe space’s key is destroyed, so its archive can no longer be opened.
5A receipt, without contentA record of what was deleted, when and by whom. None of the memory itself.
INFRASTRUCTURE
Plain words, no small print. If something here does not match what you see in your account, we want to know.
Protected storageDedicated, write-protected archive bucket
XChaCha20-Poly1305256-bit keys, encrypted before it leaves
HTTPS everywhereEvery request to the archive is signed
Secrets outside the DBMaster key and credentials in server config
Least privilegeStorage credential limited to its own bucket
Not used for trainingAI requests follow commercial, no-training terms
WHY IT COMPOUNDS
A platform that grows with every tool, every user and every run
EVERY TOOLReuses every moduleNew tools start with permissions, connectors, memory and metering in place, so they ship faster and cost less to build.
EVERY USERAdds contextTasks, notes and decisions build a memory that makes each tool more useful the longer a team works in it.
EVERY RUNIs metered and visibleAccess plus usage, with the price shown before each run that has one. Revenue grows with use, without new subscriptions.
See the framework at work
Start free with 1 € of welcome credit, or talk to the team.
framework v0.2.2