Menu

Services

Custom software development & engineering.

Software built around your needs: applications, APIs, integrations, automations, and internal tools. From an initial idea to an existing product, the technology and scope are chosen for the project.

Ways we can work together

Start with what you need to build or improve. Scope, technology, deliverables, and acceptance criteria are agreed for each project.

Custom Software DevelopmentWeb and desktop applications, APIs, and internal tools, built from scratch or as part of an existing product.

What you receive

  • A defined scope, milestones, and acceptance criteria.
  • The agreed software, with tests for its core workflows.
  • Usage documentation and an agreed technical handover.

Scope & prerequisites

Outside the initial scope

Extra features, third-party costs, and ongoing operations or maintenance unless included in the proposal.

Before implementation

We clarify users, workflows, integrations, and delivery needs before selecting the technology. A paid discovery phase may be proposed when requirements or feasibility need investigation.

Performance & Stability AssessmentA bounded investigation into slow startup, expensive runtime behavior, crashes, or data correctness risks.

What you receive

  • Evidence-backed findings within the agreed environment.
  • Prioritized bottlenecks, risks, and unresolved questions.
  • A practical correction plan and recommended next steps.

Scope & prerequisites

Outside the initial scope

Implementation, continuous monitoring, incident response, and guaranteed performance gains. A security audit is a separate scope.

Before implementation

The assessment is the paid deliverable. Reproduction constraints and access requirements are agreed up front; implementation can be proposed separately.

Features & IntegrationsFeatures, APIs, and protocol integrations for existing applications and client/server systems, including C++/Lua runtimes.

What you receive

  • An agreed feature or integration in your application or service.
  • Explicit version boundaries and acceptance criteria.
  • Validation against the agreed criteria and a technical handover.

Scope & prerequisites

Outside the initial scope

Whole-codebase ports, universal compatibility, unrelated features, and ongoing maintenance unless agreed separately.

Before implementation

A paid assessment may be needed for undocumented APIs or protocols, legacy code, uncertain dependencies, or unclear compatibility requirements.

Tooling & AutomationTools and automations for repetitive tasks, data workflows, diagnostics, builds, and development operations.

What you receive

  • A focused tool or automation for an agreed workflow.
  • Defined inputs, outputs, and failure behavior.
  • Usage documentation and a maintainable handover.

Scope & prerequisites

Outside the initial scope

A full application or SaaS platform belongs in a custom development scope. Unlimited integrations, continuous operations, and redistribution without the necessary rights are not included.

Before implementation

A paid assessment may be needed when the workflow, data formats, environment, or packaging rights require investigation.

Domain experience · OpenTibia

Client, server & tooling engineering.

OpenTibia is one domain where I apply this work. Experience across Canary, OTClient, and Remere's Map Editor covers C++/Lua integration, protocol compatibility, runtime performance, data safety, and asset workflows.

Each proposal names the supported base, versions, dependencies, and delivery boundary. Full server bases and ongoing support for an unlimited set of forks are outside these engagements.

Work involving code or asset packaging starts with the applicable licenses and distribution rights. Public code remains subject to its original license.

Explore the engineering portfolio

A clear path from idea to handover

  1. Brief

    Share your idea or problem, intended users, goals, timeline, and budget range.

  2. Assess

    Clarify requirements and feasibility, with paid discovery or investigation when needed.

  3. Agree

    Define scope, technology, deliverables, dependencies, and acceptance criteria in a proposal.

  4. Implement

    Execute the approved work within the agreed technical boundary.

  5. Hand over

    Review the agreed criteria, deliver the work, and document the next steps.

Start with an idea or a problem to solve.

A short briefing is enough to begin. Technical access and sensitive materials can wait until the scope and confidentiality arrangements are clear.