Projects

Products we build for ourselves

We open up the tools we wrote to run our own operations: both MCP servers are entirely free, MIT licensed and open source — download them and run them on your own infrastructure. Alongside them sit the enterprise platforms we deploy and operate.

TEKMER Portal — application, board review and tenant management for KOSGEB TEKMERs

The portal we built for Alanya TEKMER is now a product. Founder applications, board reviews, office and rent tracking, document verification and KOSGEB TEKMER API sync in one panel. Network and hotspot management, fingerprint and card access control and a private file space for startups plug into the same panel. iOS and Android apps included.

See details →

hetzner-mcp — an open-source bridge from AI to your servers

An MCP server for reading and operating Hetzner servers from an AI client. "How full is that disk" goes straight to Hetzner and the answer comes back to the client. Deletes and rebuilds are off by default. Free and open source, MIT licensed.

See details →

coolify-mcp — an open-source bridge from AI to your Coolify projects

The same idea on the Coolify side. Every application, database and service across all your instances in one search, with log reading, environment variables and deploy triggering included. Free and open source, MIT licensed.

See details →
Tech Stack

Modern, proven, enterprise-grade.

We pick the right tool for every project. Here's the stack we work with every day:

1 Frontend
Next.js · Astro · React · Vue · React Native · Flutter
2 Backend
Node.js · .NET · Go · Python · Java
3 Data
PostgreSQL · ClickHouse · Redis · Kafka · Snowflake
4 Cloud & DevOps
AWS · Azure · GCP · Kubernetes · Terraform
5 AI
OpenAI · Anthropic · LangChain · pgvector · RAG

Ready for your next software project?

Book a free 30-minute discovery call with our team.

Start a Project Learn more →
Certifications

Our network and cyber security work is carried out by a team holding internationally recognised Cisco certification.

Cisco CyberOps Associate badge

Cisco CyberOps Associate

Issued by Cisco · Holder: Devrim Tunçer

A certification covering security operations centre (SOC) competency: security monitoring, incident response and analysis of network attacks. It is the foundation we rely on for intrusion detection, log correlation and post-incident response work.

Verify on Credly Our cyber security service

Cisco CCNA Training

expired

Cisco training certificate · completed January 2023

Covers networking fundamentals: routing, switching, IP addressing and network security. The knowledge base we draw on for enterprise network setup and segmentation.

LinkedIn announcement Our network infrastructure service

Where enterprise data sits is not a configuration detail

Why the location of your files became a legal question

When a cloud file account is opened, the data is written to a data centre in a region you did not pick, under a key hierarchy you did not create. The contract calls this "global infrastructure". In practice it means something else: the encryption key sits with the provider, the record format is the provider's preference, and which jurisdiction your data falls under is not your decision. GDPR and Türkiye's KVKK both treat cross-border transfer as a separate legal regime, and in an audit the answer to "where is the data" has to be a document rather than a screenshot. Nextcloud is deployed precisely to produce a concrete answer to that question — files, calendar, calls and collaborative office editing under one roof, on a server in Türkiye or the EU whose address you know.

Installation on its own is not a delivery. We stand the infrastructure up, connect authentication to your existing directory service, write the backup policy down, and train administrators and end users in separate sessions. Updates, monitoring and support then run inside the same contract. This is the enterprise platform side of what we do; the open-source tools listed on this page are the other half.

What Nextcloud actually puts on the table

Files sit at the core. The desktop client syncs a chosen folder both ways, the mobile app carries the same tree, and a browser user sees the same version. A share link can be narrowed by expiry, password and download permission, so a link sent to an outside party does not have to open the whole internal folder. Version history is kept per file and deleted content waits in the bin for the length of the policy. Accidents happen; so do recoveries. A presentation a colleague overwrote can be rolled back without an administrator stepping in — that quiet recovery turns out to be the most-used Nextcloud feature in the field.

Talk brings voice and video into the same interface, with end-to-end encrypted meetings, screen sharing and chat in one window, and a room that can be attached directly to a folder or a task. For two users behind NAT to find each other, TURN and STUN services have to be configured separately — most of the video-quality complaints we hear come from exactly there. On the office side Collabora Online opens docx, xlsx and pptx in the browser with live co-editing. Calendar, contacts and task lists connect to the phone's built-in apps over CalDAV and CardDAV, team folders are set up per department, and the AI assistant handles summarisation, translation and meeting notes on your own server.

Infrastructure: Docker AIO, PostgreSQL, Redis and the encryption layer

We run the Nextcloud installation through Docker AIO. Application, database, cache, office engine and media server live in separate containers, each with its own resource limit and its own update schedule. That separation shortens the maintenance window — updating the office engine does not require stopping the file service, and users do not notice. It also buys portability: when the server has to change, the configuration moves as it is instead of being rebuilt — the flexibility enterprise Nextcloud deployments are noticed for at hardware-renewal time.

We prefer PostgreSQL on the database side; its behaviour under concurrent write load is predictable and its backup tooling is mature. Redis does two jobs — session and metadata caching, and file locking. The second matters more than it looks: without a lock mechanism, two clients syncing the same file produce conflict copies and the user cannot tell which version is right. Encryption is built in two layers: data at rest under AES-256, traffic between browser and server over TLS 1.3. Key management stays on your side, not in a third party's vault. On top of that sit access controls — second factor for administrator accounts, session limits, IP restrictions and a detailed access log.

Nextcloud Enterprise versus Microsoft 365 and Google Workspace

The first difference is data location. In subscription models data is distributed according to the provider's regional plan and you are not shown which copy sits in which data centre. On your own server the address is known, the disk is known, and the second location the backup goes to is known. The second is licence economics: in a subscription, cost grows linearly with headcount, while a self-hosted Nextcloud licence model does not create a per-user line when you add someone — hardware capacity draws the limit. For businesses with seasonal staff that difference changes the whole annual figure. The third is customisation: on an open-source platform you can rebrand the interface, narrow the app list, add your own workflow and set up single sign-on over LDAP or Active Directory. The fourth is ease of exit — files in a standard directory structure, calendar over CalDAV, contacts over CardDAV, file access over WebDAV.

The other side of the coin deserves writing down too. A subscription is not the wrong choice in every case. For a five-person team, an office without a server, or an operation already embedded in a ready-made ecosystem, running your own infrastructure is extra weight. The threshold usually arrives with three things: user count rising, data volume growing, and a concrete regulatory obligation appearing. If two of those three are on the table the arithmetic changes; if they are not, we say plainly that you should stay on the subscription.

The operating burden, migration and what sets the price

Self-hosting does not remove update, patch, disk-expansion and hardware-failure work — it moves it. A version upgrade becomes a calendar item, a disk has to be seen before it fills, and an unrenewed certificate means nobody logs in on Monday morning. So we put every Nextcloud system we build under monitoring: disk usage, service health, certificate expiry and backup results are tracked against thresholds and the alert lands before a user notices. Patches run in a monthly window, tested on a copy first and moved to production at a planned hour. Capacity is measured rather than guessed — a team that switches camera upload on consumes far more space within months than anyone predicted.

Migration starts with an inventory: which folder belongs to whom, which share links are still open, how many accounts are genuinely used. Transfer tooling from Microsoft 365 and Google Drive preserves the folder tree, sharing information and, in most scenarios, version history; calendars and contacts move in standard formats. The real difficulty is habit, so we do not cut over in a single night — the two systems run in parallel for a period, the new environment becomes the default and the old one goes read-only. On price we write no numbers here. Nextcloud is sized by usage pattern rather than headcount, and there is no per-user licence line, so cost comes from two headings — infrastructure and operations — shaped by concurrent load, storage and retention policy, integration work, backup policy and the support level you need. A figure quoted before user count and data volume are known only misleads the person hearing it.

Frequently asked questions

Where exactly does our data sit?
In the location we choose together — inside Türkiye or in the EU — on a server whose address you know. The disk is known, and so is the second location backups are written to. Key management stays on your side rather than in a third party's vault, which is what lets you answer a cross-border transfer question with a document instead of a screenshot.
Does it work with our existing user accounts and email?
Yes. Authentication connects to your existing directory service over LDAP or Active Directory, so single sign-on works with the accounts people already have and leavers are removed in one place rather than two.
Will our Office file formats break?
Collabora Online opens and saves docx, xlsx and pptx directly, with no conversion step in between. Small differences can appear in legacy files with complex macros or unusual formatting, so we test your critical templates before migration rather than assuming. Users who prefer their installed desktop office application are not blocked — the file opens from the synced folder and the server version updates on save.
Does the AI assistant send our data outside?
No. The assistant runs on your own server: summarisation, translation and meeting notes are processed on your hardware and the data does not reach an external service. That has a hardware cost — capacity for running a language model has to be planned separately, driven by how many people use it concurrently and what response time you expect.
Who handles Nextcloud updates and incident response?
We do. Version upgrades, plugin compatibility, certificate renewal, disk expansion and responding to monitoring alerts run inside the maintenance scope. If you have a system administrator in-house we define in writing which task sits with whom — most of the disruption we see comes from that boundary being left unwritten rather than from anything technical.
If we leave, how do we get our data out?
By standard means. Files sit in an ordinary directory structure on the server and can be pulled over WebDAV or straight from a disk copy. Calendars and contacts are exported, a database dump is handed over, and administrator passwords, configuration files and system documentation are part of the handover. We do not build an arrangement that makes leaving hard.