Services

Clear engineering for real systems.

Shape the work your product, application, or production system needs with the problem, outcome, scope, and next step made clear.

Service systems

A clear engineering surface for every scope.

Each service follows the same technical rhythm: make ownership, scope, and the next useful step visible.

01Build

Product & SaaS Engineering

We shape product architecture and build the critical path across frontend applications, backend services, databases, authentication, APIs, and production foundations. The result is a SaaS system that can support real users, clearer ownership, and the next release without treating every feature as a rewrite.

Technology stack

  • Next.js
  • React
  • TypeScript
  • Node.js
  • PostgreSQL
  • Prisma
  • Docker
Explore service
product.config.tstypescript
01const product = {
02 frontend: "Next.js",
03 backend: "NestJS",
04 database: "PostgreSQL",
05 orm: "Prisma",
06 auth: "session-based",
07 api: "REST",
08 runtime: "Docker",
09 delivery: ["build", "ship", "operate"],
10}
02Build

Custom Web Application Engineering

We turn complex workflows into maintainable web applications: customer and operator screens, dashboards, business rules, data models, authentication, APIs, and useful automation. Each surface is connected to the same source of truth so the application reduces manual work instead of adding another disconnected tool.

Technology stack

  • Next.js
  • React
  • TypeScript
  • NestJS
  • PostgreSQL
  • Tailwind CSS
  • Docker
Explore service
workflow.config.tstypescript
01const workflow = {
02 surface: "Next.js",
03 roles: ["operator", "admin"],
04 states: ["draft", "ready", "done"],
05 api: "NestJS REST",
06 persistence: "PostgreSQL + Prisma",
07 auth: "session + roles",
08 jobs: "background tasks",
09 automation: "webhooks",
10}
03Platforms

WordPress Development

We engineer custom themes, plugins, Gutenberg blocks, structured content, WooCommerce flows, REST integrations, migrations, and performance improvements. The work keeps editorial teams productive while giving the WordPress codebase clearer extension points and safer behavior as content, commerce, and integrations grow.

Technology stack

  • WordPress
  • PHP
  • Gutenberg
  • WooCommerce
  • JavaScript
  • MySQL
  • Composer
Explore service
wordpress-stack.phpphp
01<?php
02namespace Mcorucu\Service;
03
04add_action("init", function () {
05 register_block_type(__DIR__ . "/build");
06});
07
08add_action("rest_api_init", function () {
09 register_rest_route("mcorucu/v1", "/scope", [
10 "methods" => "GET",
11 "permission_callback" => fn() => current_user_can("edit_posts"),
12 ]);
13});
04Platforms

Shopify Development

We build and extend Shopify storefronts with Liquid themes, custom sections, commerce UX, app or extension surfaces, Admin API and GraphQL integrations, and operational automation. The stack is shaped around catalog, checkout, merchandising, and the team that must run the store after launch.

Technology stack

  • Shopify
  • Liquid
  • JavaScript
  • GraphQL
  • Node.js
  • TypeScript
Explore service
shopify-flow.liquidliquid
01{% assign product_id = product.id %}
02
03{% if product.available %}
04 <div data-product-id="{{ product_id }}">
05 {{ product.title | escape }}
06 </div>
07{% endif %}
08
09{%- comment -%}
10Admin API: GraphQL + metafields
11{%- endcomment -%}
05Platforms

CMS Development

We design content models, editorial workflows, permissions, localization, and API-driven delivery around the CMS that fits the organization. That can include WordPress, Joomla, Drupal, or a headless boundary, with integrations and publishing rules that keep content structured and reusable.

Technology stack

  • WordPress
  • Joomla
  • Drupal
  • PHP
  • Node.js
  • GraphQL
  • MySQL
Explore service
content.model.tstypescript
01const contentModel = {
02 fields: ["title", "slug", "body", "locale"],
03 locales: ["en", "tr"],
04 workflow: ["draft", "review", "published"],
05 permissions: "role-aware",
06 delivery: "REST + GraphQL",
07 search: "indexed",
08 ownership: "editorial team",
09};
06Systems

AI, Automation & LLM Integration

We place AI features inside real product workflows: provider APIs, structured outputs, validation, queues, webhooks, and human review where the decision needs control. The surrounding application code, logging, fallback behavior, and operational limits make automation useful without turning it into an opaque dependency.

Technology stack

  • OpenAI
  • TypeScript
  • Node.js
  • REST API
  • Docker
  • n8n
Explore service
automation.policy.tstypescript
01const automation = {
02 trigger: "approved webhook",
03 provider: "model boundary",
04 output: "structured JSON",
05 validation: "schema + policy",
06 queue: "human review",
07 retry: "bounded backoff",
08 fallback: "manual workflow",
09 telemetry: "traceable",
10};
07Systems

API & Systems Integration

We connect REST and GraphQL systems through authenticated contracts, webhooks, data synchronization, background jobs, and retryable workflows. The integration work includes mapping ownership and failure states so third-party changes, duplicate events, and partial outages can be diagnosed and recovered without silent data drift.

Technology stack

  • REST API
  • GraphQL
  • Webhooks
  • Node.js
  • TypeScript
  • NestJS
  • Redis
Explore service
integration.contract.tstypescript
01const integration = {
02 transport: ["REST", "GraphQL"],
03 auth: "OAuth 2.0",
04 webhook: "signature verified",
05 sync: "idempotent",
06 queue: "retryable jobs",
07 retry: "exponential backoff",
08 errors: "observable",
09 recovery: "replayable",
10};
08Systems

Cloud, DevOps & Reliability

We prepare Docker-based environments, reverse proxies, Cloudflare boundaries, health checks, CI and release paths, monitoring, backups, and recovery procedures. The goal is a production path the team can inspect and operate, with fewer surprises between a tested build and the system serving users.

Technology stack

  • Docker
  • Nginx
  • Cloudflare
  • Linux
  • GitHub
  • PostgreSQL
  • Monitoring
Explore service
release.pipeline.ymlyaml
01services:
02 web:
03 build: .
04 restart: unless-stopped
05 healthcheck:
06 test: ["CMD", "curl", "-f", "http://localhost/health"]
07 interval: 30s
08 depends_on:
09 app:
10 condition: service_healthy
11monitoring: enabled
12rollback: documented
09Improve & Operate

Software Modernization & Migration

We assess inherited code, upgrade frameworks and dependencies, refactor risky boundaries, modernize APIs, and improve performance or reliability in deliberate slices. Incremental migration keeps the system useful while each change creates evidence for the next replacement decision instead of forcing an unsafe rewrite.

Technology stack

  • TypeScript
  • PHP
  • Node.js
  • React
  • Next.js
  • Docker
  • PostgreSQL
Explore service
migration.plan.tstypescript
01const migration = {
02 adapter: "legacy boundary",
03 api: "typed contract",
04 flag: "new-runtime-enabled",
05 data: "expand → migrate → contract",
06 replacement: "incremental",
07 compatibility: "measured",
08 rollback: "available",
09 evidence: "tests + telemetry",
10};
10Improve & Operate

Production Rescue

We diagnose application failures, broken deployments, database or API problems, and performance incidents using logs, health checks, and the current release history. The work stabilizes the important path first, then documents remediation, rollback, and the ownership needed to prevent the same failure from returning.

Technology stack

  • Docker
  • Linux
  • Nginx
  • Cloudflare
  • PostgreSQL
  • Redis
  • GitHub
Explore service
recovery.runbook.tstypescript
01const checks = [
02 "health endpoint",
03 "database connection",
04 "queue depth",
05 "dependency status",
06];
07
08const recovery = {
09 first: "stabilize",
10 rollback: "last-known-good",
11 logs: "preserved",
12 handoff: "documented",
13};
11Improve & Operate

Engineering Partner

We provide ongoing senior engineering ownership across architecture decisions, feature delivery, code review, releases, maintenance, and production continuity. The relationship keeps roadmap context connected to the system in front of the team, so important technical work does not disappear between vendors, tickets, and urgent fixes.

Technology stack

  • GitHub
  • Docker
  • TypeScript
  • Next.js
  • Node.js
  • WordPress
  • PostgreSQL
Explore service
partner.cadence.tstypescript
01const cadence = {
02 planning: "weekly scope",
03 review: "architecture + code",
04 implementation: "owned delivery",
05 testing: "before release",
06 release: "small and traceable",
07 maintenance: "scheduled",
08 ownership: "shared context",
09 continuity: "production ready",
10};