Farleda
EN

Status

Release status & operations.

This page explains the published release state and our service dependencies. It is maintained manually and does not measure whether a service is reachable right now.

Information reviewed: 13 October 2026 · No live availability measurement

How to read this page

Three things worth knowing before you rely on it.

  1. Release labels show the configuration used to build this website. They are not health checks.
  2. The free consumer beta is planned for 31 October–31 December 2026. Production use is targeted for early 2027, subject to readiness.
  3. No measured uptime or automated incident feed is published here. To report an issue, use the help page.

Components

The full surface — nothing omitted because it looks unfinished.

  • Marketing website

    This page

    Public information

    Static information and product preview. Contact is by email; online forms are not yet enabled.

  • Journey planner

    Before release

    Beta entry

    The free open beta is planned from 31 October 2026. App access and online registration are not yet open.

  • Passport verification & public API

    Before API release

    Separate from the app

    The verification interface follows the public API release setting. A valid signature checks the integrity of a calculation record; it is not proof of completed travel.

  • Website forms & email

    Not yet enabled

    Contact by email

    Beta, pilot and programme interest can be discussed personally by email. A message is not a newsletter subscription.

  • Website hosting

    Provider information

    Contabo · web-01

    The information website is served statically on web-01. This page is not an automated health check. The app requires a separate release.

  • External data services

    Third-party services

    Availability varies

    Route planning and other features depend on external data sources. Coverage, freshness and availability vary by source; see the data inventory for details.

Release settings are updated with a website build. Runtime failures may therefore not appear here immediately.

How we communicate disruptions

The commitments; the operational detail sits in the incident policy on the trust page.

  • Report a problem

    Use Help & feedback, including the affected page or route, the time and a short description.

  • Partner communication

    Pilot-specific contacts, response times and service commitments belong in the individual agreement.

  • Product changes

    Published changes are collected in the changelog. This is separate from live service monitoring.

Incident history

No operational incident history is maintained on this page yet. This does not establish that no incidents have occurred.

Reporting a problem

Three addresses, three different jobs.

  • Something looks broken

    hello@farleda.eu — please include the URL, the time (with timezone) and what you expected to happen.

  • Security vulnerability

    Contact security@farleda.eu; if delivery fails, use office@stoicera.com. Start with a brief description without sensitive data. Disclosure terms and scope are on the security page; machine-readable contact at /.well-known/security.txt.

  • Pilot partners

    Use the contact agreed for your pilot. Response commitments follow your contract.

For help, use Help & feedback. Product changes: changelog. Provider information: provider inventory.