Manorsoft · MerTek Platform · MTP

Reusable core for product delivery.

MerTek Platform (MTP) is Manorsoft's shared application core and generator toolchain. It turns canonical product specs into generated, testable, observable software.

Built for repeatable delivery. Shared packages, generators, service plumbing, ops patterns, and repo-ready tooling.
Start a platform discussion Commercial licensing, implementation, modernization, and support conversations are open.

What MTP is

MTP is not a single web app. It is the reusable platform Manorsoft uses to build and modernize applications where contracts, code, runtime behavior, and operational evidence need to stay aligned.

A reusable product core

Shared libraries, conventions, and runtime patterns give each project a stable foundation instead of rebuilding identity, events, state sync, jobs, telemetry, migrations, and deployment wiring from scratch.

A spec-driven delivery system

Canonical models describe entities, service calls, events, payloads, database shape, client behavior, tests, and operational hooks. Those models become coordinated artifacts across the stack.

A toolchain for teams and agents

Human engineers and AI-assisted agents work inside bounded, machine-readable contracts, so implementation stays focused on product logic instead of fragile glue code.

Inside the platform

From model to running software

MTP uses a common source of truth to generate server code, client code, service and event surfaces, binary data contracts, database artifacts, test scaffolds, telemetry hooks, and deployment materials. The result is a system where requirements, implementation, and runtime evidence can be reviewed together.

  • Canonical contracts Data, workflow, service, event, client, and operational definitions stay readable by people and tools.
  • Generated scaffolds MerGen fans a change across the service, client, database, binary payload, and test surfaces that need to move together.
  • Observable runtime Telemetry, recent-call metrics, background-job traces, and admin diagnostics make delivery reviewable after code ships.

Core

MerGen

Spec-driven generation for services, clients, data, tests, and runtime surfaces

Data

MerBuf

Compact, typed interchange for explicit payload contracts and low-overhead transfer

Services

Events

Generated service calls, server events, client sync, and operational telemetry

Platform modules

MTP can be adopted as a full application platform or in narrower modules that strengthen an existing product.

MerGen

Generates coordinated C#, JavaScript, TypeScript/mobile, MerBuf, SQL, service, client, event, and test outputs from canonical metadata.

MerBuf

Provides compact, typed binary interchange for payloads that need explicit contracts, lower bandwidth, and predictable parsing.

Client state sync

Generated client transports, cache updates, sequence tracking, reconnect, replay, and event handling keep web and mobile experiences current.

Service and event pipeline

Generated HTTP and WebSocket surfaces connect applications to real-time workflow updates, sequence tracking, reconnect, replay, and cache updates.

Identity and access

Access tokens, device and session tracking, provider integration hooks, throttling, and admin controls give projects a consistent security surface.

Jobs, data, and deployment

Background jobs, migrations, partitioning, generated SQL, Docker-based starters, backups, and environment flags make operations repeatable.

How MTP works

A disciplined path from product intent to software that can be generated, tested, observed, and reused.

  1. Model the product contracts

    Entities, workflow, services, events, payloads, jobs, database changes, client behavior, and operational hooks are captured in canonical specifications.

  2. Generate the coordinated surfaces

    MerGen creates the server, client, mobile, binary data, SQL, event, and test artifacts that need to agree across the repo.

  3. Implement bounded business logic

    Engineers and agents fill the intentional gaps: product rules, integrations, adapters, user workflows, and domain-specific behavior.

  4. Verify through harnesses and telemetry

    Generated tests, runtime diagnostics, recent-call metrics, and structured events help teams compare implementation behavior against the spec.

  5. Ship through repeatable operations

    Deployment starters, environment patterns, migrations, backup flows, and maintenance controls keep each repo easier to promote and support.

Adoption paths

New products

Start with a repo-ready foundation for application code, data contracts, generated clients, service calls, events, and deployment workflow.

Modernization

Wrap legacy systems with typed service/event contracts, generated client surfaces, migrations, telemetry, and safer rollout patterns.

Integration layers

Use MTP as the application-services layer for workflows that need identity, background jobs, data synchronization, and operational evidence.

Platform licensing

Adopt selected modules, the generator workflow, or the full platform with Manorsoft implementation and support.

Where MTP helps

Reusable platform work for products, enterprise tools, and mission workflows.

Custom software Application modernization Systems integration Data engineering Generated APIs Real-time web and mobile Membership platforms Content and commerce Internal operations tools Federal mission software

“MTP exists because repeatedly hand-wiring the same services, events, clients, tests, and deployment hooks is wasteful. The platform keeps the contracts machine-readable, so people and agents can build from the same source of truth.”

Aaron Murray · Founder, Manorsoft

Build with MerTek Platform

If your team needs a reusable platform for generated contracts, real-time application services, typed data interchange, and repeatable delivery, MTP is ready for a focused technical discussion.

Request a briefing

Licensing, implementation, modernization, and commercial support conversations are open.