Skip to content
{{ mobileFrame }}
{{ pixelField }}

Software that {{ heroWord }}

We build, improve and look after the software your business runs on.

what we do

One team for the whole life
of your software.

{{ r.title }}{{ r.k }}
{{ r.k }}

{{ r.title }}

{{ r.short }}

We handle{{ d.t }}
You receive{{ g.t }}
how we work

A clear,accountable process.

Four defined stages. Each one has an owner, a decision point and a deliverable you can review before we move on.

before & after

Sound familiar?Here's what changes.

BeforeWith CyberTabby
{{ r.b }} {{ r.a }}

Six services One Accountable Team

Take one, or the ones you need
— as a project or an ongoing service.

{{ s.num }} · {{ s.k }}

{{ s.title }}

{{ s.short }}

We handle
  • {{ d }}
You receive
{{ g }}
sound familiar?
“{{ h }}”

SupportLevels

Each request moves up only as far as it needs to — and every level ends with a clear output.

L1first line

Intake, classification, SOP checks and user guidance

Ticket and first-line action
L2diagnosis

Logs, configuration, known issues and workarounds

Diagnosis and workaround
L3root cause

Advanced application, integration and code-level diagnosis

Root cause and recovery plan
L4fix & release

Source diagnosis, agreed defect fixes, testing and release

Approved patch & release evidence

Major features and upgrades use a separate approved work package. A scheduled service is not a continuously staffed 24×7 service.

ManagedApplication Services

Support and maintenance for enterprise business systems — each area with a clear output.

User & incident supportL1/L2 ticket intake, SOP checks, log analysis and known-issue recoveryTicket records, diagnosis and user updates
Technical maintenanceL3/L4 code diagnosis, approved defect fixes and regression testsRoot-cause records and validated patches
Change & releaseImpact review, approved deployment, validation and rollback preparationChange approval and release evidence
Operational knowledgeCode baselines, runbooks, access reviews and continuity rehearsalsMaintained knowledge and readiness records

Engineering &Project Support

Approved work packages extend the application service.

maintenance & changeKeep it improving
  • Source-code fixes and configuration changes
  • Regression testing and release preparation
  • New features and workflow enhancements
  • Documentation and operational handover
project continuationPick up where others left off
  • Support an in-flight project after handover
  • Continue integration and UAT activities
  • Assist go-live and stabilization
  • Coordinate site and platform dependencies

Major upgrades, new projects and on-site delivery use a separate approved scope, staffing plan and estimate.

ServiceBoundaries

We own the application layer. Everything around it keeps a named owner.

Area
CyberTabby
You or your provider
Application
Code, configuration, diagnosis, approved fixes and releases
Business decisions, authorization and acceptance
Connected systems
Application-side messages, logs and fault isolation
Operation and support of counterpart systems
Infrastructure
Application requirements and recovery coordination
Cloud, servers, OS, DBA, network and platform backup
Equipment & site
Software behaviour and interface coordination
Physical equipment, automation and site safety

Hosting and permanent on-site staff are not included unless separately agreed.

services / {{ sv.k }}{{ sv.num }} / 06

{{ sv.title }}. {{ sv.short }}

what we doScope agreed per engagement
{{ d.n }}{{ d.t }}
what you receive
{{ g }}
sound familiar?
“{{ h }}”
questions

{{ f.a }}

Clear scope Visible Ownership

At every stage you know who decides
— and what you get.

Getting Started

From the first message to kick-off — four simple steps.

  1. First conversation

    You tell us what the system does and what needs to change.

  2. Discovery review

    We look at the workflow, the code and the people involved.

  3. Proposal

    Scope, responsibilities, acceptance and timing — in writing.

  4. Kick-off

    Access is set up, owners are named, work begins.

Four stagesOne Clear Path

  1. 01

    Understand

    We review your workflow, code, interfaces and support runbooks, and confirm scope and access.

    who decides
    You and us, together
    you get
    Scope & ownership map
  2. 02

    Agree

    Responsibilities, acceptance criteria, access and timing are confirmed.

    who decides
    You approve
    you get
    Work plan & agreement
  3. 03

    Deliver

    We build, review and test, then release with approval, test evidence and a rollback plan.

    who decides
    We run it, you accept
    you get
    Tested release & evidence
  4. 04

    Support

    We triage and escalate tickets, confirm recovery with users, review ageing tickets and keep known issues current.

    who decides
    Agreed service scope
    you get
    Runbook & change log

Ways to workTogether

fixed scope

Project

A defined build or improvement with a clear scope and handover.

monthly

Ongoing support

Maintenance and user help within an agreed service scope.

rolling

Improvement plan

A steady backlog of enhancements, released on a rhythm.

transition

Takeover

We receive code and documents from another team, prove we can build and run it, and carry it forward.

scheduled

Standby & continuity

A weekly session alongside your current team — assigned L1–L4 work, release readiness and rehearsals — ready to take over when authorized.

Who does what?

you bring
A named decision maker
Access to systems, code and environments
Knowledge of how the business uses the system
Timely feedback and acceptance
Named owners for infrastructure and site
Written authorization for production changes
we bring
A named delivery owner
Reviewed, tested changes with a rollback plan
Clear progress updates and release notes
Documentation the next person can use
Named accounts with least-privilege access
Ticket status and incident reporting

What youReceive

Documents you keep, whatever happens next.

Scope &
ownership map
Discovery
Work plan & agreementAgreement
Test evidenceDelivery
Release notesDelivery
RunbookSupport
Change logSupport

Staying In Touch

No chasing for updates.

One point of contact

A single owner who knows the work.

Shared backlog

Everything requested, visible to both sides.

Regular updates

Progress, risks and decisions — written down.

Release notices

You know what changed, and when.

Three rulesWe Work By

They apply to every project and every support request.

own it

Visible ownership

Every task and decision has a named owner on both sides.

test it

Controlled changes

Reviewed, tested and released with a rollback plan.

write it

Usable documentation

Written for the next person who has to act.

ServiceControls

A visible ticket workflow and clear production authority.

Ticket ownershipA named owner, priority and escalation path for each request.
Production changesAuthorized approval, test evidence and a rollback plan.
Service reportingTicket status, handling effort and recurring-incident trends.

Service hours, response targets and workload capacity follow the agreed service schedule.

Taking overA System

From the first handover to day-to-day support — with evidence at every step.

prepare
01
Code custodyReceive code, history and dependencies. Build and deploy independently, keep a version baseline.
02
PilotRun one real workflow end to end — test a failure, prove recovery and rollback.
03
Full handoverComplete the inventory, configuration and SOPs, confirm roles, run a full rehearsal.
operate & return
04
StandbyA weekly session with your current team on L1–L4 tickets, releases and rehearsals.
05
ActivationWith written approval, check versions, access and data, then lead application support.
06
ReturnWhen authorized, hand back code, history, runbooks and open issues — with sign-off.

KnowledgeTransfer

A structured handover — with proof the new team can repeat the work.

Application knowledge
In the sessionArchitecture, workflows, site differences and dependencies
Proof you receiveApplication inventory & open-question log
Build & deployment
In the sessionThey demonstrate, we repeat, they review
Proof you receiveIndependent build & deployment record
Operational support
In the sessionTicket walkthroughs, logs, known issues and escalation
Proof you receiveRunbook & supervised ticket evidence
Recovery & release
In the sessionFault diagnosis, approved fix, rollback and rehearsal
Proof you receiveTest results, recovery record & sign-off

Security &Controlled Change

Delivery controls that align with your approved security requirements.

Identity & accessNamed accounts, least privilege and approved production access.
Access approvalsPeriodic review
Code & dependenciesVersion baseline, reviewed changes and a dependency inventory.
Change recordComponent register
Data & environmentsMasked test data and controlled handling of logs and secrets.
Environment recordsData-handling records
Release & recoveryTest results, approval, a release log and a rollback procedure.
Release evidenceRecovery record

Specific security remediation or certification needs a defined control baseline and an agreed work package.

We areCyberTabby

A Thailand-based software engineering and application-support team. We build and maintain business applications, integrate operational systems and provide ongoing technical support.

based in
Thailand
working with
Teams in Thailand & abroad
focus
Software for organisations
scope
From development to live support
engagement
Projects or ongoing service

Meet the Team

Four teams, one way of working — each with a named owner for your system.

Software Engineeringengineering
Builds and improves business applications, web apps and APIs.
BackendFrontendMobile web
Application Supportsupport
Handles L1–L4 tickets, diagnosis, fixes and user updates.
Service deskDiagnosisMaintenance
DevOps & Releasedelivery
Owns source control, test environments, releases and rollback.
CI/CDEnvironmentsRelease
Integration & Continuitycontinuity
Connects systems, runs handovers and keeps runbooks current.
APIsHandoverRunbooks
in one sentence

We help build, improve and look after the software businesses use to work.

As a defined project, or as an ongoing service under agreement.

What we Offer

Six services — as a project or an ongoing service.

Who we Work For

Need a teamto build

Companies that need developers to create, modernize or extend the software they run on.

Need a teamto look after it

Companies whose software is live and needs someone accountable for it — including a backup team for business continuity.

in Thailand and abroad

Where we Focus

Engineering and ongoing support — for the systems businesses run on.

Warehouse & retailStock, orders, store and online-sales workflows.
Operations & financeEnterprise operations, revenue, cost and invoicing.
IoT & connected devicesSensor data, device APIs and analytics.
Web & mobile appsModern, responsive applications for daily work.
Working modelRemote, English-language delivery — alongside your team, the previous vendor and your platform providers.

SelectedExperience

Four anonymized profiles from the delivery team’s project experience. Client and product names are omitted.

industryprojectwhat was neededwhat we did
Warehouse & retailWarehouse app and online salesA local operator needed software for warehouse and retail workflows, alongside online sales.Workflow discovery, application delivery, online sales functions and ongoing maintenance.
Retail financeWeb and mobile modernizationA retailer wanted easier end-to-end use of its existing financial system, on web and mobile.Process review, a modern web frontend, responsive mobile access and production support.
TelecommunicationsBusiness-system replacementOperations depended on legacy order, revenue, cost and invoice workflows linked to other systems.Interface mapping, data migration and reconciliation, directory access, cutover and maintenance.
Retail technology / IoTDevice APIs and analyticsA platform combined sensor data, device management and reporting across software versions.Version-aware integration, sensor-event mapping, reporting views and diagnosis.

Case studies reflect the team’s experience prior to and during the company’s formation.

What we Work With

Technical experience — that supports repeatable operations.

backend & data
backend.stack
language: Java · Spring Bootruntime: Node.js · TypeScriptdatabase: SQL · PostgreSQL · SQLite
frontend & automation
frontend.stack
ui: React · Next.jsui: Vuescripts: Python · Shell
build & delivery
delivery.stack
source: Gitbuild: Mavenpipeline: CI/CD

Build and delivery use your approved Git, CI/CD and deployment environments.

Build useful softwareHelp Keep It Running

Business applications, integrations — and the practices behind them.

{{ careersBoard }}

How we Hire

Four steps — clear and respectful of your time.

step 1ApplySend your CV and a short note through the role page.
step 2ConversationA call with the hiring team about the role and your experience.
step 3PracticalA short, relevant exercise — paid if it takes longer than an hour.
step 4DecisionWe reply to every applicant by email.

Roles are published only on this site. We never ask candidates for payment or bank details.

{{ careersDetail }}

Let's talk aboutYour System

Development, support, an integration, a takeover or a continuity standby — describe what should change.

[email protected]To arrange a short first conversation.
Thailand & worldwideRemote, English-language delivery.
Keep it safePlease don’t include passwords or production data.

Looking for a job?

send an enquiry
Please check the highlighted fields.
Service{{ cErr.interest }}

Used only to respond to your enquiry. Privacy notice

✓

Thank you. Your enquiry has been received. We’ll reply by email to arrange a conversation. Reference: {{ cReference }}

Initial Working Session

What we cover together — in the very first session.

  1. agenda 1InventoryReview the application and site inventory.
  2. agenda 2InterfacesMap interfaces and service responsibilities.
  3. agenda 3Starting pointSelect the onboarding workflow and environment.
  4. agenda 4Handover planDefine knowledge transfer and acceptance.
  5. agenda 5AgreementAgree scope, service hours and capacity.
let's talk

Have a systemto build or look after?

What happens next
Tell us about the systemWhat it does, who uses it and what needs to change.
We reply to arrange a callA short conversation to understand the situation.
Agree scope and next stepsClear responsibilities before any work begins.