Support

Questions about your account, a payment, or a result that does not look right? Get in touch — we read every message and aim to reply as quickly as we can.

Email us
The fastest route, and the only one that does not need an account. Best for billing, invoices, and anything urgent.
Open a ticket
Keeps the conversation, and any screenshots, in one thread you can come back to. Requires a FERS Cloud account.

Billing & subscriptions

Managing your plan

Everything is self-service from your profile page. Manage subscription opens the secure Stripe billing portal, where you can update your payment method, download invoices, or cancel. Cancelling stops the next renewal — you keep Pro until the end of the period you have already paid for.

What things cost

  • Free — the full solver, every analysis type, for models up to 100 members, plus 100 SDK/MCP solves per week. No card required.
  • Pro — €19.95 per month or €199.00 per year, for models up to 10,000 members, plus cloud storage. Renews automatically until you cancel.
  • Solve credits — prepaid, for SDK and MCP solves beyond the weekly free quota, at €0.01 per solve. A one-off purchase rather than a subscription.

Prices are in EUR. VAT is calculated at checkout from your billing country, and you can enter an EU VAT number there.

Refunds

New Pro subscriptions carry a 14-day money-back guarantee — email us within 14 days of the first payment and we will refund it. After 14 days fees are non-refundable, as set out in the Terms of Service.

A charge you do not recognise

Payments reach your statement through Stripe. If a charge looks wrong, email support@ferscloud.com with the date and amount before opening a dispute with your bank — we can almost always sort it out faster than a chargeback can.

Reporting a solver or result problem

Structural results are hard to diagnose from a description alone. Sending these four things usually turns a long exchange into a single reply:

  1. The model. Export it to JSON from the editor and attach the file — it is the only way to reproduce exactly what you ran.
  2. What you expected, and why — a hand calculation, a textbook case, or a result from another run.
  3. What you got instead — the quantity, the member or node, and the load combination.
  4. Any message shown on screen, copied verbatim, plus a screenshot if the problem is visual.

To check FERS against a reference solution yourself first, the benchmarks page runs analytical and NAFEMS cases live in your browser.

Answers without waiting