Current product status

Gabion exists and is being developed. Standalone access does not exist yet.

Gabion is currently provided to Pikiner clients together with the migration of a working product to a new stack.

The technology and its architectural principles are described on this site, but it is not yet possible to download the Runtime, buy a separate subscription, obtain a public trial, or create a new project on your own.

We separate the public information available about Gabion from access to the tool itself.

Practical access to Gabion currently goes to clients of the Pikiner migration service.

After the handover the client receives two different results:

1. a standalone application project;
2. licensed access to the project edition of Gabion for the first year.

The delivered project

The client receives a separate application directory on the agreed stack:

• Java;
• Spring;
• PostgreSQL;
• TypeScript;
• Thymeleaf;
• CSS;
• Flyway.

The project holds:

• the source code;
• the business logic;
• the frontend and the backend;
• the data structure;
• the migrations;
• the tests;
• the configuration;
• the deployment files;
• the documentation.

The project has to build, deploy, and run without an active connection to Gabion.

The project edition of Gabion

The client receives access to Gabion in order to continue developing the specific delivered product.

The exact contents are determined by the license and may include:

• the Gabion Runtime;
• MCP tools and resources;
• architectural checks;
• diagnostics;
• the browser UI;
• the supported AI integrations;
• the updates provided;
• help with Gabion to the scope established.

Limits of the current access

The project edition:

• applies to one delivered project;
• does not create a right to an unlimited number of new projects;
• does not transfer the source code of the Runtime;
• does not provide the internal module storage;
• does not provide the internal module-management CLI;
• does not allow Gabion to be distributed or resold;
• does not automatically include future features;
• does not include continuous production support.

The Gabion limits do not apply to the client's right to own, change, and operate the delivered project.

What happens after the first year

The client can:

• renew access to Gabion;
• continue development without Gabion;
• bring in another team.

Not renewing ends the licensed features of the tool, but not the operation of the production application.

What does not exist yet

The following are not available now:

• public download of the Runtime;
• buying a subscription on your own;
• a free trial;
• a personal token for an arbitrary project;
• an open beta;
• use of gabion init by a new external user on their own;
• public access to the module storage;
• an open module marketplace;
• automatic booking of a Gabion Live Showcase.

Gabion Live Showcase

A Showcase is not a way to obtain Gabion or to start a trial.

For a suitable project, Pikiner can hold a separate free technical meeting after seeing the client's product.

At the first meeting the client demonstrates their product to Pikiner.

At a Gabion Live Showcase the Pikiner team demonstrates to the client:

• a prepared project;
• the Runtime;
• work with the AI;
• a real error;
• the diagnostics;
• the correction;
• the repeated check;
• an independent build.

Taking part in a Showcase:

• does not provide a token;
• does not create a client project;
• does not open the Runtime for standalone use;
• does not guarantee that a project is accepted for migration;
• does not reserve a future plan.

The current access is a project license after a Pikiner migration. A Showcase is a separate demonstration meeting, not a trial.

Detailed Terms for Pikiner Clients Show Your Working Product to Pikiner

Gabion is already in use as a production technology, but standalone distribution requires more than a working runtime.

Before external access is opened, the following have to be prepared:

• a stable installer and updates for every platform stated;
• documentation for users that works without the Pikiner team;
• clear product editions and license boundaries;
• management of organizations, users, projects, and tokens;
• support and rules for responding to defects;
• a compatibility policy and updates to the production pipeline;
• secure distribution of modules;
• observability and diagnostics without disclosing client data;
• a Privacy Policy, a DPA, and rules for working with external LLMs;
• billing, cancellation, and reinstatement of a subscription;
• a procedure for reporting a vulnerability;
• a scenario for removing the product and user data.

Limited access now is a boundary of responsibility, not artificial scarcity.

This sequence describes a direction of development, but it is not a release calendar.

1. 1. Pikiner clients — available now

   Gabion is used with a product that has been migrated into a known production pipeline. The Pikiner team knows the architecture of the project and can observe real usage scenarios.

2. 2. Web studios — planned

   Professional teams that build several client projects could become the first standalone external scenario. It requires management of projects, licenses, modules, and responsibility toward the end customer.

3. 3. Individual companies — planned later

   Internal product teams will require corporate access management, a data policy, integration with their own AI infrastructure, and a predictable support lifecycle.

4. 4. Individual developers — a long-term direction

   Wide standalone access will require the most complete documentation, safe defaults, self-service diagnostics, and support for a large number of different environments.

The order may change after experience with real users. No future stage has a public date until it is announced separately.

Web studios are considered a possible first audience for a separate product, because they work on repeatable architectural tasks and can assess Gabion on several real projects.

For a future program it is important to understand:

• the size and composition of the team;
• the type of products created;
• the current stack;
• the AI assistants in use;
• the number of new projects per year;
• client requirements for code and IP;
• requirements for local models and data;
• the level of support required;
• readiness to work with a limited early version;
• the ability to provide structured feedback.

Telling us about an interest does not mean admission to a program and does not create a queue with a guaranteed place. If an early access format is approved, Pikiner will contact suitable teams separately.

A company can state its requirements in advance, even though a standalone enterprise edition is not available yet.

It is particularly useful to describe:

• the number of teams and projects;
• how AI is used in development;
• the permitted LLM providers;
• requirements for local or private-cloud inference;
• SSO, 2FA, and role management;
• audit trail requirements;
• outbound traffic restrictions;
• internal rules for working with code and data;
• SLA and support requirements;
• the security team's process for reviewing a new tool.

If a company already has a working product that has to be migrated off a prototype stack, it can consider the Pikiner service now. That is access to the project edition of Gabion, not an early enterprise plan.

Show Your Product to Pikiner

It is not currently possible to download Gabion, buy an individual subscription, or obtain a personal token for a new project.

You can tell us which scenario you would like to use the technology for. That information helps determine future editions and documentation priorities, but it is not registration for a beta with an announced date.

It is useful to state:

• the operating system and architecture;
• the main stack;
• the AI tool in use;
• a cloud or local model;
• the type of project;
• the main problem Gabion is expected to solve;
• readiness to take part in testing and to provide feedback.

The form is for exploring future standalone access models and technology partnerships.

It does not create:

• a Gabion account;
• a trial;
• a token;
• a new project;
• a place in a beta;
• a Live Showcase booking;
• a promise of a price;
• a promise of a launch date;
• an obligation for Pikiner to answer every enquiry.

If you already have a working product and are considering migrating it, use the separate Pikiner form.

Show Your Product to the Pikiner Team

Do not send source code, production data, personal data of your users, passwords, API keys, or other secrets.

The first version of the form has no file upload.

After submission the form is recorded as an enquiry of the corresponding type.

What happens next depends on the purpose selected: future product access, a technical question, a partnership, or another proposal.

If this is interest in future access

If a suitable model is approved, Pikiner may contact individual teams for a new conversation and to check whether the interest is still current.

If this is a technical question

The team can:

• answer in writing;
• add the answer to the FAQ;
• ask for clarification;
• point to an existing technical page;
• keep the question for future documentation;
• not answer individually, if the question requires disclosing closed details or has no confirmed answer yet.

If the question concerns the internal engines, the Runtime, the manifest, the module lifecycle, or another complex technical mechanism, the answer may require further internal verification.

In that case Pikiner comes back with a verified written answer rather than improvising during a conversation.

A public answer must not disclose:

• the source code of the Runtime;
• internal endpoints;
• credentials;
• ways to circumvent the license;
• confidential client data;
• the internal module storage;
• information that increases security risk.

If this is a partnership proposal

Anything further begins only after a separate written agreement.

If this is an investment proposal

The enquiry is directed to the appropriate Pikiner representative, if such a process is approved.

The form must not be used to send:

• bank details;
• identity documents;
• contracts;
• financial statements;
• a confidential deck;
• credentials;
• other sensitive attachments.

Closed material is transferred only after the recipient and a secure channel have been agreed.

If the visitor actually wants a migration

If the text makes it clear that a company has a working product and needs a migration, the reply has to direct it to the Pikiner process.

The enquiry and its data must not be moved automatically into another system without a basis disclosed in the Privacy Policy.

At the first meeting the client demonstrates their product to Pikiner. A Gabion Live Showcase may be offered separately later.

Show Your Product to the Pikiner Team

A Gabion Live Showcase is not created by the form

Submitting the availability form:

• does not book a Showcase;
• does not guarantee a Showcase;
• does not set a date;
• does not replace the qualification of the project by Pikiner;
• does not provide the Runtime;
• does not provide a token.

For a migration client, a Showcase is offered after a preliminary check of the applicability of the working product.

Subscribing to updates

If the visitor has separately consented to receive future messages, their email may be used in accordance with the wording of that consent.

The visitor has to be able to:

• unsubscribe from the messages;
• identify the sender;
• see why they received it;
• get a link to the Privacy Policy;
• request deletion in the procedure provided.

The absence of a separate consent does not prevent a reply on the substance of the current enquiry, if such contact is permitted by the applicable legal basis.

Storage of the enquiry

Before the form is launched it is necessary to determine:

• the storage system;
• the data owner;
• the retention period;
• the range of recipients;
• employee access;
• the possible processors;
• the deletion rules;
• the procedure for a user request;
• the backups;
• the access logs.

Enquiries must not be kept indefinitely merely because the date of the public launch of Gabion is not yet known.

Analytics

The contents of the fields must not be sent to a product analytics system.

It is acceptable to measure technical events of the form, for example:

• opening the page;
• starting to fill it in;
• a successful submission;
• a general error.

An analytics event must not contain:

• the name;
• the email;
• the company;
• free text;
• the stack;
• the models;
• the data requirements;
• the partnership proposal.

The form records an interest. Access appears only after a separate product and contractual decision by Pikiner.

The public material explains: the workflow; the Runtime; the modules; the manifest; MCP; models and data; the independence of the application; the terms for Pikiner clients.

How Gabion Works Technology Gabion for Pikiner Clients Frequently Asked Questions

For a working product — Pikiner. For future standalone access — the interest form. Neither path is a public trial of Gabion.