Version 1.0 · Effective: August 27, 2026 · Entity: AiTrade LLC, a Florida limited liability company
CounselPublication date — set the effective date above to the date this page actually goes live at railcall.ai/legal/licensing.Counsel — registered addressCounsel supplied the jurisdiction of formation, and the entity line above now reads "AiTrade LLC, a Florida limited liability company". The registered business address was not supplied and is not published anywhere on this site — we have not invented one. Provide it for the entity blocks.This is a notice of fact, not an agreement. It states which licence applies to which part of RailCall, who holds the copyright, what the licence does not cover, and what may change later. Nothing on it takes any right away from anyone.
This page carries no “published for review” banner, and that is deliberate. Counsel settled the question on 27 August 2026: a factual licensing notice carries no review banner, because marking a statement of what is already true as unreviewed undercuts the legal certainty of the open-source release it records. The banner is scoped to the Trademark Policy, which states rules we may revise rather than facts already fixed by releases we have shipped.
RailCall Station, RailHub Studio, and the RailCall CLI ship under the MIT License. Every release published to date is MIT, permanently, including the right to sell. Fork it, run it, change it, build a business on it. You do not need our permission, an account, a key, or a conversation with us.
What MIT does not hand you is our name. The code is yours to use; the marks are not. And the services we run — the gateway, the Marketplace, the dashboard — are governed by our Terms of Service, because those are things we operate, not things you downloaded.
Under the MIT License, with any RailCall release you hold:
Run it anywhere, at any scale, in production. No node count, no seat count, no run count, no revenue ceiling.
Run it commercially. Inside a for-profit company, at a competitor, in a regulated environment, on customer workloads. MIT does not distinguish.
Modify it, and keep your modifications private forever. You never have to publish, contribute, or describe them.
Fork it, publicly or privately, under your own name — subject only to §5 below on what you call it.
Build commercial products on it and sell them. Products, services, hosted offerings, appliances.
Redistribute it, modified or not, including bundled inside something you charge for.
Sublicense it, as MIT expressly permits.
Never register, never phone home, never tell us. There is no activation, no licence key, and no entitlement check standing between you and the code you downloaded.
Stay where you are. If you like a release you already have, keep it. Nothing we publish later reaches backwards, and choosing not to upgrade is not a violation of anything.
The one condition MIT attaches: keep the copyright and permission notice in copies and substantial portions. That is the whole obligation.
Counsel / Founder — check against “premium protocol upgrades”The eighth item above says there is “no activation, no licence key, and no entitlement check standing between you and the code you downloaded.” That is true of every release shipped to date. It is not obviously compatible with the live pricing page, which advertises “premium protocol upgrades, à la carte” as one of three things we charge for. If that phrase describes paid components of the Software, then something does stand between a customer and some code, and this list and Terms §10.3 both need a paragraph explaining what and how it is checked. If it describes a hosted Service, the pricing page should say so. Resolve before this page publishes — a licensing page that promises no entitlement check while the price list sells one is precisely the contradiction this package exists to remove.| What | Where it comes from | Licence today |
|---|---|---|
| RailCall Station — the released artifact (railcall_station.tar.gz), every release up to and including station-v1.5.8, published 25 August 2026 | GitHub Releases on github.com/patl4588/railcall-core | MIT. The LICENSE file ships inside the tarball. |
| patl4588/railcall-core — public source | GitHub | MIT. The repository does not yet carry a root LICENSE file. It should, and we are adding one. Our position is unambiguous and stated here in the meantime: this code is offered under MIT. |
| patl4588/railcall-cli — public source, including the CLI, the companion daemon, the vault drivers, the receipt signer, and the standalone verifier that install.sh fetches | GitHub | MIT, on the same basis and with the same fix pending. |
| RailHub Studio — the free desktop client, the signed macOS app bundle | GitHub Release assets | MIT for RailCall's own code. Bundles third-party components under their own permissive licences — see §7. |
| Third-party components inside the app bundle | npm and PyPI upstreams | Their own licences (MIT, Apache-2.0, BSD-2/3, ISC). Those licences and notices govern those files, not ours. |
| Hosted services — the gateway, the Marketplace, the dashboard, sign-in, and licence/entitlement issuance | railcall.ai | Not a software licence question. Governed by the Terms of Service. |
| Code we have not published | — | Nothing is offered until it appears in a release. Unpublished code carries no grant, and none is implied. |
The licence text shipped in every release is the standard MIT License, with this notice line:
Copyright (c) 2026 MeterCall contributors
"MeterCall" is what the project was called before it was RailCall. "Contributors", plural, is deliberate and accurate — see the next section.
Copyright in RailCall is held by the individual people who wrote the code. AiTrade LLC holds copyright only in the contributions its own personnel made — in the same way every other contributor holds theirs. No contributor has assigned their copyright to the company, and the company does not claim ownership of the codebase as a whole.
Separate copyrights, not joint ownership. The distinction is not pedantry, and an earlier draft of this page got it wrong by saying copyright is “held jointly.” Under US law a joint owner of a work may grant a non-exclusive licence in the whole of it without asking the others — so claiming joint ownership would have meant claiming we could relicense the entire codebase unilaterally, which is both more than we hold and the exact opposite of the constraint the next paragraph relies on. What actually exists is a body of separately owned contributions, each licensed to the public under MIT by the person who wrote it.
We state this for two reasons. The first is that it is true, and a licensing page that misstates who owns the code is worthless for the only purpose such a page has. The second is that it is a real constraint on us, and it is why the forward-looking notice below commits to a version-forward-only change rather than a retroactive one: a licence change reaching code we do not own is not something we could do by publishing a page, and it is not something we could do by agreeing with ourselves either. It would take the consent of the people who wrote it.
If you contributed to RailCall, you still own what you wrote.
CounselConfirm the ownership formulation above, and confirm it against employment and contractor agreements: work made for hire by AiTrade personnel vests in the company, but a contributor engaged without a written IP assignment generally keeps their copyright even when paid. Terms of Service §3.3 and §16.1 use the same formulation and should be read alongside this.Counsel / Ops — forward-only fix, high value, cheapNothing currently gates new commits, so every commit that lands without a sign-off deepens the constraint described above. A Developer Certificate of Origin check, or a lightweight CLA, applied to future contributions only, needs nobody’s retroactive consent, costs a CI action, and is what makes §6’s forward notice meaningful rather than theoretical. It does not fix the existing history and is not represented as doing so. Confirm whether to adopt DCO (lower friction, no rights transfer) or a CLA (more optionality, more friction), and note it on this page once adopted so contributors know before they submit.MIT is a copyright licence. It licenses code. It does not license trademarks, and it never has.
RailCall, RailCall Station, RailCall CLI, RailCall Marketplace, RailHub — which names both our hosted organizational platform and RailHub Studio, the free desktop client — and the RailCall logo are marks of AiTrade LLC, a Florida limited liability company. Publishing the code under MIT does not license them, and no clause of MIT can be read to. The complete list, with the status of each mark, is at Trademark Policy §1.1.
Read that sentence for exactly what it says, and not for more. RailHub Studio is on the list because its name is a mark. The client itself is MIT-licensed — §3 above records it, and the release you download carries the MIT text. Neither the mark nor this section makes it proprietary, restricts what you may do with the code, or adds any condition to the MIT grant. This section limits what you may call the thing you ship, and nothing else. If you fork the client, you keep every MIT right in §2, and you give it your own name.
You may, freely and without asking:
You may not:
Fork the code and ship it — that is what the licence is for. Ship it under your own name.
Full terms are in the RailCall Trademark Policy.
CounselConfirm the published URL for the Trademark Policy so this link does not point at a 404. RAILHUB is claimed here as of 2026-08-27, matching the marks list at Trademark Policy §1.1, and its scope covers both the hosted platform and RailHub Studio, the free desktop client. Registration status is still open: this page asserts common-law marks and no registration, and no ™ or ® designation appears anywhere on the site. Because RAILHUB now spans a downloaded product and a hosted service, any filing needs to be assessed in the goods class as well as the services class — flagged at Trademark Policy §1.1 and not decided here.The software licence covers software you run. It does not cover a service we run for you.
The RailHub platform, the hosted gateway, the Marketplace, the dashboard, sign-in, and licence/entitlement issuance are operated by us on our own infrastructure. RailHub Studio is not in this list — it runs on your hardware, so it is Software under §3 and MIT, and only the parts of it that call a service we operate touch the Terms. Access to the services listed here is governed by the Terms of Service and, for the Marketplace, by the Marketplace Terms. Those documents may set conditions the software licence does not — rate limits, acceptable use, fees, suspension for abuse — because they govern a different thing.
Neither of those documents narrows the software licence. If one of them appears to restrict what you may do with code you already hold, that is a drafting error on our side and this page governs. Tell us and we will fix it.
MIT does not include an express patent grant.
CounselState the company's position on patents here. The options are (a) say nothing, which is the MIT default and what every MIT project does; (b) publish a standalone non-assertion covenant for the released versions. (b) is the stronger trust signal and costs nothing if there is no patent portfolio.The MIT licence covers copyright. It does not grant any right in our trade marks, and it never did — that is true of MIT everywhere, not a condition we added. What that means in practice is set out in §5.1 above and in the Trademark Policy: fork the code freely, ship it under your own name.
Counsel / Ops — the notice that makes §5.1 enforceableThis is written on a website, and the people it most needs to reach have never visited it. Roughly 685 release tarballs have shipped carrying a LICENSE file and no trademark notice, so a forker sees MIT, sees nothing about the marks, and reasonably concludes there is nothing to see. Two cheap, forward-only fixes, both of which strengthen every clause of the Trademark Policy against someone who never read it: (1) add aTRADEMARK.md to the released artifact and to each public repository, and (2) add a short notice section to the README and to NOTICE — “RailCall and RailHub are trade marks of AiTrade LLC. They are not licensed by the MIT licence covering this code; see railcall.ai/legal/trademark.” Neither needs anyone’s consent and neither changes the code licence.Counsel / Ops — three more, same categoryEach is free or nearly so, none needs contributor consent, and each closes a gap this page currently documents rather than fixes. (1) Land the root LICENSE files. §3 above states that patl4588/railcall-core and patl4588/railcall-cli carry no root LICENSE. Until they do, those repositories are default all-rights-reserved to a reader, and the MIT position rests on this webpage. They should land before the page documenting their absence publishes. (2) Move the repositories under a company organisation. Releases ship from a personal GitHub account; the entity asserting the marks should be the entity distributing the goods, because use-in-commerce evidence attaches to the owner. The transfer is free and materially improves the trademark record. (3) Encryption export notification. The product ships Ed25519 signing and installs worldwide from a curl script. Terms §2.4 puts export compliance on the user and says nothing about the company’s own obligation; published-source encryption software has a one-time notification path under 15 CFR 742.15(b), and the signed desktop app needs mass-market treatment. It is one email, and it is a standard enterprise procurement question.We may, in the future, publish new components or new versions of RailCall under different licence terms. We are not announcing that today, and no such release exists. But saying "this will always be MIT no matter what" would be a promise about a company that does not exist yet, and we would rather tell you the shape of any future change now than surprise you with it later.
Counsel / Founder — the homepage says the oppositeThis section reserves an option that the live marketing says we have already given up. Fetched 2026-08-27,railcall.ai carries “Nothing here is gated, metered, or seat-counted — and it stays that way,” “This is the part that never changes and never costs anything,” and “This is the free layer everything else is built on, and it stays free.” A reservation of rights is weakest exactly where the marketing promised permanence, and the four commitments below are worth much less if a customer can point at those sentences. Terms of Service §3.5 carries the identical conflict and the identical note. Either soften the homepage to “free today, and any change is version-forward only, never retroactive” — which is what this section actually promises and is still a strong claim — or narrow this section to new components only. It is one sentence of homepage copy now, and an estoppel argument later.If we ever do it, four things will be true, and we are committing to them here:
Nothing on this page, and nothing we publish later, modifies, conditions, revokes, or reaches back to the MIT grant already delivered in every release to date. That grant is delivered. It is not ours to take back, and we are not trying to.
The Studio app bundle redistributes third-party open-source packages under permissive licences (MIT, Apache-2.0, BSD-2/3, ISC). Those components are governed by their own licences and notices, which travel with them and are not superseded by ours.
We are adding a consolidated NOTICE file listing every bundled component and its licence to the app bundle and to the release artifact. Until it lands, ask at legal@railcall.ai and we will send you the current list.
Licensing questions, including "is what I want to do allowed" — legal@railcall.ai, or the RailCall Discord.
We answer these in writing, and where an answer is generally useful we publish it here so the next person does not have to ask. If the honest answer to your question is "MIT already lets you do that", that is the answer you will get.
Counsel / OpsVerify legal@railcall.ai reaches a monitored human before this page publishes. Support is Discord-first and the transactional email provider is wired but dormant.Entity: AiTrade LLC, a Florida limited liability company · Governing law: Florida · Last updated: August 27, 2026
See also: Trademark Policy · Terms of Service · Marketplace Terms