This blueprint is a personal experiment by the Head of Logistics, exploring how AI tools can be leveraged in eFTI platform development. It serves as an example and a practical starting point for anyone who wants to get started with Vibe coding for the eFTI platform.
The blueprint is not a final implementation guide, nor a ready-made production solution. Its purpose is to support planning, lower the barrier to getting started, and help developers get moving. Each developer is nevertheless responsible for their own final production implementation, its compliance, and its technical solutions. Always make sure to verify up-to-date requirements from official sources during implementation.
What is the blueprint about?
AI tools have developed enormously in recent times. At the same time, Vibe coding has become an acceptable alternative for software development. For the eFTI platform, Vibe coding is particularly interesting, because the implementation is guided by requirements coming from regulation as well as the APIs provided by the Gate side. This brings clear structure and boundaries to the development work, which is why it suits Vibe coding well.
The Head of Logistics wanted to explore, in practice, how AI tools work as a support for eFTI platform development, and built his own eFTI platform through Vibe coding during the summer of 2026. So that the experiment would not remain just one person’s learning experience, it was decided to compile the implementation into a blueprint and share it openly for everyone to use as a starting point for development.
The goal is to share lessons learned, open up a practical way of proceeding, and offer a concrete starting point for those who want to try AI-assisted development in their own eFTI project. The blueprint therefore serves above all as support for learning, planning, and getting started.
Why aren’t we sharing a finished implementation?
Fintraffic and Traficom are not implementing an eFTI platform for companies to use. Therefore, sharing a finished implementation could cause confusion about who is responsible for the solution and what purpose it is intended for. Even though, as a personal project, the implementation could in principle be shared as open source code, a blueprint is in this case a better way to support the ecosystem and clearer in terms of responsibility for the implementation. In other words, everyone is responsible for their own outcome, even if they use the blueprint as a basis.
Thanks to Vibe coding, the finished blueprint makes it possible to quickly access a basic solution for the platform. Give the blueprint to an AI tool as a basis and guide the implementation in the direction you want.
An invitation to try it out
We hope this blueprint inspires you to try AI tools in your own eFTI project. It doesn’t offer a ready answer to everything, but it can help you get moving.
Read the blueprint document here
Happy vibe coding,
Teemu Heikura