La Passerelle: connect your tools and monitor your services, simply
La Passerelle connects your systems through their APIs and monitors your servers, your websites and your certificates. Message content is erased after processing.
Status: built and validated in-house and not marketed. I designed Passerelle to see how it would turn out, to learn, and to estimate the server load such a service represents. The automation market is very competitive and launching the offer was not worth the cost to me. The project was very rewarding, but I chose to keep it for my own personal use, so no access is offered. This page is a technical overview of that project, which is part of my work.
Two families of features
Connectors
Link your software through their APIs: data from one feeds the other, with the transformations needed in between.
Monitoring
Watch your servers by ping, your websites by HTTP request with interpretation of the response, and your certificates.
La Passerelle in pictures and video
Screenshots of the application, with fictitious data: light and dark themes, desktop and mobile. The demonstration below lasts about 1 min 9 s.
Video transcript
- 00:00 You sign in to Passerelle with a demonstration account. The cookie banner is declined.
- 00:10 Monitoring first sorts what needs your attention.
- 00:14 The list shows your four flows, all active.
- 00:18 A flow opens on its transformation steps: filter, script, message rebuild.
- 00:21 The trigger shows the flow’s entry address and how it receives messages.
- 00:24 The destinations receive the transformed message. They can be paused at any time.
- 00:28 The trial applies the steps to a sample message. Nothing is sent.
- 00:31 The result shows each step and the message obtained.
- 00:35 The history lists received messages with their delivery status.
- 00:39 A failed message shows the cause and what to do: here, a rejected address.
- 00:44 Retrying puts the delivery back in the queue. It fails again as long as the cause remains.
- 00:48 Monitoring tracks a website, a server and a certificate.
- 00:53 Each check is kept with its duration and detail.
- 00:57 The Account page shows your profile and your organisation.
- 01:01 Password change and member management happen in the same place.
What sets it apart
- Hosted by OVH SAS: see the legal notice.
- Content erased after processing: kept 7 days after a failure so it can be retried, 24 h in debug mode; 30-day history.
- Simple and effective: a direct interface, no overcomplication.
- A credit model, no subscription: credit bundles that do not expire, free filters and fields, a failure costs nothing.
A few examples of use
- Send each new order from an online store to invoicing software.
- Pass form requests on to a customer relationship tool.
- Be warned when a server or a website stops responding.
- Stop finding out that a certificate has expired because browsers warn your customers.
Design: the credit model studied
The model studied was based on pay-as-you-go credits, with no subscription. 1 unit is one script step run or 3 successful sends; filters, fields and monitoring checks are free, and a failure costs nothing.
The credit model studied for La Passerelle
As La Passerelle is not marketed, no price is offered. Here is the credit model I had studied, presented as a design example: one unit is one script step run or 3 successful sends; filters, fields and monitoring are free.
Technical overview of a completed project, not marketed. La Passerelle was built and validated in-house; no access, purchase or subscription is offered. See the work.
Frequently asked questions
Can I use La Passerelle?
No: it was built for my own personal use and is not marketed. If you have a similar need, I can build it for you: get in touch.
How does it differ from automation services such as Zapier?
La Passerelle follows the same idea, connecting applications through their APIs, with three choices: hosting at OVH, message content erased after processing, and pay-as-you-go credits with no subscription.
Is my data kept?
Message content is erased after processing; it is kept 7 days after a failure so it can be retried, and 24 h in debug mode. The message history (without the content) is kept 30 days. Connector secrets are encrypted and never displayed again.
What can be monitored?
Servers by ping, websites by HTTP request (the response is interpreted) and certificates. Monitoring details.
How are credits calculated?
1 unit = 1 script step run to the end, or 3 successful sends. Filters and fields are free, and a failure costs nothing.
Which connectors are available?
Slack, Discord, Microsoft Teams, Google Chat, email (Brevo), Airtable, HubSpot, Intercom, Zendesk (ticket), Pipedrive, Google Sheets, SFTP, WhatsApp (free-form message or template), email to members and generic HTTP request, plus your organisation’s custom connectors. Details.
Did credits expire?
No: in the model studied, credits did not expire.
What happened when credits ran out?
Flows refused new messages (error 402). A single alert email was sent when less than 15 days of credit remained, based on the pace over the last 14 days.
La Passerelle is an independent project. Zapier and the other brands mentioned belong to their respective owners.
A similar need?
I design custom integrations and tools: describe your need in a few lines.