meilynx

For AI solution providers

One gateway per customer. One console for all of them.

Each hospital or bank you serve gets its own Meilynx gateway in your cloud account. Your team sees every customer in one place and sets each one's policies, and every change is recorded as made on that customer's behalf.

solution provider console · 4 customers
  • Hospital Areporting
  • Hospital Breporting
  • Bank Creporting
  • Medical center Dnot reporting

one gateway per customer

Deployment

Your account, your gateways.

Gateways run next to your product, in your own cloud account, one per customer. Customer data stays there, and requests reach the model only after the PHI and PII the gateway detects are redacted. Meilynx receives each call's outcome (allowed, redacted, held, refused), the policy that applied and counts, with no prompt, reply or tool-argument content.

Your cloud account · customer data stays here

Your product

agent · voice · chat

Gateway · customer A

its own policies

Gateway · customer B

its own policies

Your engineers

read a redacted copy on the gateway

requests after redaction; calls to permitted records

Anthropic models

directly or through Amazon Bedrock

Each customer's record system

outcomes · policies · counts

Meilynx

your console · each customer's view

Models

Anthropic, directly or through Amazon Bedrock

Added latency

<5 ms p95 added latency, measured under sustained load (Oct 2026)

Customer data

In your cloud account

The console

Every customer, in one view.

Your team runs the service across customers from the console. Each customer's gateway, release, posture and open items sit side by side.

Customers · 4Sorted by open items
CustomerIndustryGatewayReleasePostureOpen
Hospital AHealth systemreportingcurrentOn track0
Hospital BHealth systemreportingcurrent2 to review2
Bank CBankreportingupdate availableOn track1
Medical center DHealth systemnot reportingcurrent1 to review1

Acting for Hospital B

Policy change: add a tool for appointment reminders. Recorded as made by your team on Hospital B's behalf.

Waiting for Hospital B

A new tool widens the agent's reach, so it waits for the hospital's approval.

  1. 01

    Every customer as a tenant

    Each hospital or bank you serve is its own tenant, with its own gateway, policies and record.

  2. 02

    Gateway health and version

    See which gateways are reporting and which run an older release, across every customer at once.

  3. 03

    Posture and open items

    Each customer's compliance posture and the items waiting on your team.

  4. 04

    Act on a customer's behalf

    Step into a tenant to set its policies. Every change is recorded as made by your team on that customer's behalf.

Policies per customer

Set what each customer's agent may do.

Four kinds of policy, set for each customer and enforced on its own gateway.

01

Tool access

Which tools the agent may call for this customer.

02

Data reach

The record types the agent may touch. A call for anything else is refused before it reaches the record system.

03

Redaction

PHI and PII the gateway detects are redacted before a request reaches the model.

04

Holds

Actions the policy holds, such as a large payment or a medication change, wait for a reviewer the customer names.

Troubleshooting

Debug a call on your own gateway.

Your engineers read a redacted copy of each call on the gateway that handled it. That content never passes through Meilynx.

Your engineer reads a redacted copy of a call on the gateway. Meilynx receives outcomes, policies and counts.Your cloud accountEngineeryour teamGatewayone customerredacted copy, read hereMeilynxno call contentoutcomes · counts
What stays with your customer

Some decisions belong to the hospital or the bank.

The reviewers your customer names keep the decisions its regulators expect it to make, and its own view shows each one.

How it reads to a hospital

Held actions

Released or declined by the reviewers each customer names. Your team sees the status, and cannot release a hold the customer's reviewer owns.

Wider scope

A change that widens the agent's reach or authority waits for the customer's approval, unless it delegated that kind of change to you.

Its own view

Each customer reads its conditions, what was enforced and each change notice, and can verify offline that the record has not been altered since it was written.

Get started

See your customers in one console

We'll set up two customer gateways and walk through the console, a policy change and a held action.

Regulatory updates

When a regulator changes what an AI examination asks for, hear about it first.

Short notes on SR 26-2, NYDFS 500, FINRA, the NAIC bulletin, the EU AI Act, and the employment-AI statutes, plus what we ship. A few emails a month.