Custom Interfaces · ASCOM · Alpaca · Legacy

Custom software is not the first answer.

Your hardware may already have the software it needs. MCAM starts by assessing the supported path before recommending custom development.

We build custom interfaces when there is an actual integration gap, not simply to replace a working manufacturer driver.

Start with Device Integration Assessment — $495 Discuss an OEM Project

Capabilities when a gap is real

ASCOM integration

Use or complete an ASCOM path after the supported driver is ruled insufficient.

ASCOM Alpaca

Networked device interfaces where Alpaca is the right target.

INDI interoperability

Where INDI is part of the installed control environment.

Protocol bridges

Serial, USB and TCP gateways between otherwise supported pieces.

Legacy adapters

Abandoned or unsupported equipment — after a $495 feasibility review. Starting at $1,500.

OEM / manufacturer

Interface engineering around hardware you build. Quote only.

How pricing works

There is no public camera / mount / focuser price matrix. Pricing depends on documentation, protocol availability, hardware access, SDK availability, firmware behavior, required interface, safety consequences, testing effort and integration scope.

Custom ASCOM / Alpaca interface engineering is available when no supported interface exists, the existing driver is abandoned or unusable, custom hardware needs an interface, a protocol bridge is required, a manufacturer needs software engineering, or a unique automation capability is required. Price is quoted after the $495 assessment. No minimum fixed checkout price is promised without a scoped estimate.

Project process

MCAM does not begin by selling custom code.

We begin by understanding the observatory, then use the supported driver first.

1 Discover

Tell us what exists and what must change.

2 Assess

MCAM reviews hardware, software and interfaces.

3 Use the supported path

Existing manufacturer interfaces are preferred where appropriate.

4 Specify

Any actual gaps are documented.

5 Engineer

Integration or custom software is built only where needed.

6 Test

Hardware and interface behavior is validated.

7 Accept

The customer verifies the agreed scope.

8 Deliver

A versioned package, documentation or report is delivered.

9 Support

Maintenance and engineering support remain available.

Final feasibility depends on device documentation, firmware, supported interfaces, SDK availability, hardware access and required test scope. MCAM does not manufacture telescopes, mounts, cameras, domes or weather stations. Third-party names identify interoperability only. MCAM does not claim universal device compatibility, ASCOM certification, manufacturer affiliation, unattended safety without validation, 24/7 support, or that every ASCOM, Alpaca or INDI client is interchangeable.