16 days ago
Hello Railway Team,
I am Carlos, CTO of Axisor Technologies Brazil. We are a software development startup focused on LLM research and AI solutions.
I am reaching out to inquire about the possibility of hosting an instance of EvolutionAPI on Railway, or potentially having it added as a template, while ensuring full compliance with your Terms of Service.
Context & Use Case: We have a product called OrionAI, which automates customer support workflows using n8n + Chatwoot + EvolutionAPI. This stack allows our clients to manage team hand-offs and streamline support tickets.
Why we need this:
We have tested the WAHA template currently available on Railway, but it lacks the specific features we need compared to EvolutionAPI (which we currently host on Hostinger).
95% of our infrastructure is already hosted on Railway. We are extremely happy with the migration and the platform's performance, and our goal is to centralize 100% of our operations with you.
Compliance Assurance: We understand the sensitivity regarding WhatsApp automation. We guarantee that this instance will strictly be used for legitimate customer support automation. We have a rigid code of conduct and will not use the platform for spam, unsolicited bulk messaging, or any activity that violates Railway's ToS or privacy policies.
Could you let us know if deploying this is acceptable or if there is a possibility of officially supporting this template?
Best regards,
Carlos CTO, Axisor Technologies
4 Replies
16 days ago
Hello,
Full compliance would mean using Meta's official API, not EvolutionAPI.
brody
Hello,Full compliance would mean using Meta's official API, not EvolutionAPI.
16 days ago
Thanks for the note, Brody.
To be clear, we actively advise all our clients to utilize Meta's Official API, and we are fully transparent about the risks and trade-offs of using unofficial gateways. However, many clients specifically request solutions like EvolutionAPI due to cost or implementation flexibility, and as a software provider, we need to support that choice.
Since WAHA (another unofficial gateway) is currently available as a template on Railway, I assumed that hosting similar tools was permitted for legitimate use cases.
Could you clarify: Is the restriction specifically against adding EvolutionAPI as a public Template (which implies Railway's endorsement), or does Railway strictly prohibit even the private hosting of such tools via Docker?
We strongly prefer to keep our entire infrastructure centralized on Railway, so knowing this distinction is critical for our migration.
Carlos CTO, Axisor Technologies
16 days ago
While we have not strictly prohibited the use of EvolutionAPI, WAHA, or similar, we do not endorse the use of anything other then Meta's official API, the existence of community made templates (such as the WAHA template) doesn't mean we endorse it either.
So while we cannot provide a template for you, you are technically free to deploy EvolutionAPI / WAHA into your private project.
brody
While we have not strictly prohibited the use of EvolutionAPI, WAHA, or similar, we do not endorse the use of anything other then Meta's official API, the existence of community made templates (such as the WAHA template) doesn't mean we endorse it either.So while we cannot provide a template for you, you are technically free to deploy EvolutionAPI / WAHA into your private project.
16 days ago
Perfect. Thank you for the transparency and the clear distinction, Brody.
That is exactly the clarification we needed. We fully understand Railway's stance on endorsement vs. private usage. We will proceed with deploying it as a private service, strictly adhering to the acceptable usage policy we discussed.
Appreciate your help in clearing this up.
Carlos CTO, Axisor Technologies
Status changed to Solved brody • 16 days ago