Avioane v1 is ready: play solo, locally, or online with a friend.Open the game menu

Public on the outside. Controlled on the inside.

Launch a SaaS people can understand before they sign in.

Bring marketing, content, community and the private application into one localized, modular product experience built to grow.

RO and EN from day onePublic, auth and restricted accessIndependently enabled modules

The problem

A fully closed product hides its own value.

When every visitor lands on a login screen, the product loses context, indexable content and the chance to build trust before conversion.

Invisible value

Features and use cases cannot be understood without an account.

SEO without content

Search engines have no substantial public pages to index.

Abrupt conversion

Login becomes the first interaction instead of the natural next step.

The solution

One product, three experience layers.

The starter clearly separates what should be publicly discoverable, what builds community and what belongs to verified users.

Public site

Landing, SEO pages, contact, legal and official content for every visitor.

Community

Discussions, Blog and Social for answers, durable content and recent activity.

Private application

Dashboard, profile, notifications, support and administration with controlled access.

Features

The modules a mature SaaS product expects.

Each module has a clear role, its own permissions and the right public or private surface.
01

Identity and access

Registration, email verification, password reset, profile, roles and permissions.

02

Discussions

Public, auth or restricted channels, replies, solutions, reactions and moderation.

03

Social

Public Explore, profiles and posts governed by visibility rules.

04

Support

Private ticketing, categories, priorities, SLA, attachments and staff workspace.

05

Notifications

Normalized events, email and an in-app center with deduplication and preferences.

Features

Content and community

Useful answers become a public asset, not lost conversations.

Discussions supports long-tail content and the knowledge base, Blog provides official content, and Social keeps the community current.Community

Trust through architecture

Verifiable product proof without invented testimonials.

The starter communicates the capabilities it actually provides. Customer logos, testimonials and commercial metrics can be added later from real data.
2

public languages

RO/EN routes and content

3

access levels

public, auth, restricted

7

core modules

integrated into one product

1

public shell

for marketing, content and community

Security and privacy

Private access stays private even when the product is discoverable.

The public area does not weaken application rules. Authorization continues to be enforced in the API and private routes.Security

Verified email

Private and write actions can explicitly require a verified account.

Roles and permissions

Operational access relies on explicit policies and permissions.

Auditability

Important actions can be tracked through audit logs and normalized events.

Protected resources

Private attachments and restricted content are served only after authorization.

Flexible pricing

Three commercial models, the same public structure.

The starter does not impose project pricing. The section supports trials, self-service subscriptions or an enterprise offer.
For evaluation

Trial

Configurable

A simple path from visitor to verified account.

  • Landing and public pages
  • Registration and verification
  • Limited module access
View the pricing model
For organizations

Enterprise

Contact sales

An offer adapted to roles, volume and operations.

  • Extended roles and permissions
  • Dedicated SLA and processes
  • Configuration and integration
View the pricing model

FAQ

Natural questions before using the starter.

Core answers remain public, while documentation and community can continue the conversation in depth.View every question

Next step

Start with a foundation that explains the product before asking for login.

Configure the project identity, content and modules, then expand the public area as real proof and SEO intent emerge.