Brücke OS
Brand: TreuLink
Advice that shows its sources. A multilingual platform for the Germany–Türkiye corridor.
ELECTRICAL & ELECTRONICS ENGINEER (B.SC.) · ANKARA
Concept, architecture and quality assurance are mine. Implementation is carried out together with AI coding agents. I started out with a soldering iron — and that still shapes how I build systems.
For public authorities, advisory bodies and recruiters: the details that are usually checked first — each one backed by a document.
I build software with AI assistance, and I say so openly. Not as a caveat but as a method: the machine writes faster than I ever could. The question that remains is a different one — who decides what gets built, and who guarantees that it is right.
mine
Problem definition, domain model, system boundaries, data model. Architecture decisions are recorded as ADRs — with the reasoning and the alternatives that were rejected.
with AI coding agents
Claude Code and OpenAI Codex, governed by agent contracts (CLAUDE.md, AGENTS.md) that set out what an agent may and may not do. On larger projects two lines run in parallel.
mine
Tests, type checking, linting, Lighthouse thresholds, security boundaries. What does not pass these gates does not ship — regardless of who wrote it.
The hard decisions in my projects were never coding questions. They were: what must this system not do? Which claim needs a source? Where does information end and legal advice begin? Those are not questions you delegate.
Brand: TreuLink
Advice that shows its sources. A multilingual platform for the Germany–Türkiye corridor.
The "localai" CLI + a real multi-device infrastructure
Where hardware meets AI systems: a security-first CLI and a lab that actually runs.
Multi-tenant corporate platform with CMS, SEO and AI visibility. Live on staging.
Search engines are no longer the only readers of a website. Alongside JSON-LD, sitemap and robots.txt, the platform ships an experimental llms.txt — machine-readable for the AI systems that increasingly sit between a customer and a company. The lead form is multi-step and triple-guarded (honeypot, Turnstile, rate limit), and consent records are pseudonymised. If the database goes down, the site still serves content from a safe fallback.
Concept, monorepo architecture (8 packages), data model, deployment pipeline and quality gates. First client: a construction company in Ankara.
An operating system for small field-service businesses
Not another CRM but a quotation engine: from a voice memo on site to a finished PDF quote.
Small firms rarely fail for lack of customer records; they fail because a quote takes three days. So the centre of the system is not the contact — it is the quote. Voice note from the phone, AI draft, human approval, PDF. A memory of materials, prices and suppliers grows with every job. Tenant isolation, RBAC and audit logging are hard security boundaries, not options.
Product concept, modular architecture, data model, worker design. Prepared for conversion into a SaaS product.
Site photos become marketing drafts — but nothing is exported until a human approves it.
The central rule lives in the code, not in the manual: the AI produces drafts only; without human approval there is no export. Every generation, approval and export is written to the audit log. The AI adapter is provider-agnostic — with no API key it falls back to a mock, which makes tests possible without network and without cost. The test suite runs PGlite in-process, so no live database is needed.
Concept, security boundaries, job-queue architecture, test strategy.
A governance platform for municipalities
Young people report what their neighbourhood lacks. The map shows where. The decision stays with people.
Two data worlds in one database: geography via PostGIS, semantic similarity via pgvector. That lets hundreds of submissions be grouped by place and by meaning at once — "three streets over, twelve young people are saying the same thing in different words". The AI classifies, summarises and raises early warnings; it decides nothing. That boundary is the project's most important requirement, not its limitation.
Concept, data model, governance rules, map integration. It grew out of my work on the Youth Executive Committee of Çankaya municipality.
The work here was not the features but the operations: backups, health checks, runbooks.
Building a website is the smaller half; running it for years is the larger one. So the project ships automated checks for backup freshness, storage health, DNS hygiene and audit-log pruning — plus smoke tests and a written runbook. Staging deploys automatically; production only on explicit approval.
Monorepo structure, CI/CD pipelines, operational automation, documentation.
A catalogue with no shopping cart. Deliberately: the sale happens on the phone, not at checkout.
For antiques and one-off items a shopping cart is the wrong metaphor — every sale starts with a conversation. So: static export, no payment provider, no session handling. Locally everything runs without Docker, Postgres or cloud storage (SQLite plus the filesystem); in production the same application runs on PostgreSQL and object storage. One data model, two environments, one build step.
Architecture, environment-aware adapters, build pipeline, unit tests.
From university, via an Erasmus+ internship in French power electronics, to independent product development.
2016
Started university, Çankaya
2018
IT internship, PTT
2020
Rement, Ankara technopark
2022
Erasmus+, power electronics, France
2023
B.Sc. graduation
2024
IT manager, Berliner Grup · telc B1
2025
Freelance · ZAB recognition
2026
Goal: systems engineering in Germany
Boards, soldering irons, a homelab — and the other side of it: events, volunteering, people.
Email is the quickest way to reach me. For questions about projects, credentials or a guided demo, just write — I reply in German, English or Turkish.