Oko

Oko is my SaaS CRM for websites and businesses. It gathers in one window what is otherwise spread over many tools: website checks, failures, enquiries, contacts, articles and statistics. I built it for my own projects; the groundwork for several clients was there from the start.

The task

Anyone running several websites loses track quickly: a certificate expires, a page drops out of search, an enquiry gets stuck between email, spreadsheet and messenger. Oko is meant to show all of it in one place – and say what to do first.

What Oko does

• Monitoring. SSL, speed, security and SEO of every site are checked daily. Every rating comes with proof: the address, the server response, the affected spot in the HTML.
• Incidents. A signal becomes a task; after “fixed” an automatic re-check follows. An incident is closed only with a fresh check as proof.
• Leads and map. Enquiries with statuses, on a map without third-party map providers. Statements about probabilities only with the number of observations.
• CRM. People, companies, orders and history. Erasing a person under the GDPR also removes every link to them.
• Editorial. News from feeds, a draft in three languages, a check of every number, approval through my assistant Hermes. This is how Klariq is made.
• Competitors. Competitor profiles and positions in Google search – only from public pages and respecting robots.txt.
• Statistics. Views without cookies or third-party scripts, plus Google Search Console data.
• AI costs. What every operation and every site costs; email addresses and phone numbers are never sent to an AI provider.

How it is built

Oko runs on Next.js and Supabase. Every table is separated by tenant and protected by row-level rights in the database. Agents and Hermes get their own access with defined rights; every action is logged. The database is backed up daily, encrypted.

Status

Oko runs every day for my websites. The next step is to offer it to others as a product.