Skip to main content
Montandon Ltd
Backend Engineering

The glue that holds
the web together.

Secure, scalable, and documented APIs. We build the endpoints that power your mobile apps, partner integrations, and internal tools.

Why Custom?

Open your business to the world (securely).

Want to let your suppliers check inventory automatically? Want to feed data into a mobile app? You need an API.

We prioritize security first. Rate limiting, authentication (OAuth/JWT), and input validation are standard.

Our API Standards

    Bank-Grade Auth

    OAuth2, JWT, and API Key management to control exactly who accesses what.

    Rate Limiting

    Prevent abuse by throttling requests per IP/User (e.g. 100 req/min).

    Versioning

    We build v1, v2, v3 so you never break existing integrations.

    Auto-Documentation

    Swagger/OpenAPI specs generated automatically from the code.

swagger.yaml
paths:
/users/{id}:
get:
summary: Get user details
security:
- bearerAuth: []
responses:
'200':
description: Successful response
content:
application/json:
schema:
$ref: '#/components/schemas/User'
Developer Experience

If it's not documented,
it doesn't exist.

The worst nightmare for a developer is integrating with a "black box" API. We treat documentation as a first-class citizen.

We provide a hosted "Developer Portal" where your partners can generate API keys, view live usage logs, and test endpoints in a sandbox environment before going live.

Trade-offs

Code vs Low-Code?

Sometimes n8n (or Zapier) is enough. But when you need scale, you need code.

n8n / Zapier Webhooks
Custom Node/Python API
Speed to Build
Instant
Weeks
Cost per Request
High (Volume Pricing)
Low (Serverless)
Complex Logic
Hard (Spaghetti)
Easy (Code)
Database Access
No (API only)
Yes (Direct SQL)
Whitelabeling
Long Running Tasks
Timeout (30s)
Unlimited (Queues)
Specs

Built to Spec.

Get Technical
RESTful Architecture
GraphQL Endpoints
OAuth2 / JWT Auth
Node.js / Python / PHP
Swagger Documentation
API Key Management

Frequently Asked Questions

We support both. REST is better for public APIs and simple integrations. GraphQL is better for complex mobile apps where you need to fetch many resources in one request to save bandwidth.

We typically use serverless functions (AWS Lambda or Vercel) for infinite scale and zero idle cost. For high-compute tasks, we use Digital Ocean Droplets or Docker containers.

We use standard JWT (JSON Web Tokens) for stateless authentication. We also implement IP allow-listing, rate limiting, and input sanitisation to prevent SQL injection.

Yes. This is common for connecting Stripe or Zoho (and HubSpot) to your own database. We build robust listeners that verify signatures and handle retries if your server is down.

Always. We commit everything to your GitHub repository. You own the IP.