TOMATo Logo
TOMATo
Architecture and operations in one model

Pure GenAI History

TOMATo with Pure GenAI

This timeline captures how the TOMATo app evolved from first production increments in February to today, including methodological progress in tool selection, skills, harnesses, help system, developer documentation, and test coverage.

AI transparency

Generative AI tools are used in the development of TOMATo and this website. This development history describes the tasks they perform and how the project came about.

Responsibility for published content rests with the operator identified in the legal notice.

Latest update

  • Layered 3D supports side-by-side or stacked layers, refined connections, and shared color and search highlighting with 2D.
  • The local licensing runtime covers signed files, settings, grace periods, mandatory watermarks and transactional quotas; the production issuer and key distribution remain pending.
  • The public website and self-hosted app are separated; Free, Pro and Enterprise are explained on a dedicated pricing page.
  • Legal notice, contact form, sitemap and visible AI transparency extend the website. SMTP was tested locally through the form; production delivery remains dependent on deployment configuration.

Product and method timeline (newest first)

Licensing and bootstrap

Licensing runtime with grace periods, watermarks and quotas

  • Signed license files and a persistent installation ID form the core. Owners/admins manage the file in settings; Free without a file, 90-day periods, login notices and atomic quotas were checked with isolated PostgreSQL and browser tests. Online requests, the production issuer and key operations remain pending.

Website and transparency

Contact, discoverability and AI disclosure

  • A legal notice, contact form with tested local SMTP delivery, sitemap and robots.txt extend the website. A compact footer links to AI transparency and development history. Production delivery requires its own SMTP configuration and distributed request limits; a complete privacy review remains pending.

3D visualization

Layer arrangement, connections and color controls expanded

  • Layers can be explored side by side or stacked. Body ports and connection paths were refined, along with person shapes and light/dark presentation. 2D and 3D share search highlighting; color changes preserve geometry and camera. The projection remains derived from shared model data.

Plans and product communication

Free, Pro and Enterprise on a dedicated pricing page

  • Free is presented with 200 managed systems, Pro starting at 1,000; Pro and Enterprise are available on request. Pricing and a dedicated licensing rules page explain limits, grace periods and watermarks. An internal ROI working model keeps assumptions separate from evidenced customer results.

Architecture and deployment

Public website separated from the self-hosted app

  • The marketing website gained its own project while the application was prepared for standalone container operation. The local entry joins both through targeted website rewrites without redirecting protected app and API areas to the website.

Website and product communication

Current MyGlass images and an updated feature overview

  • Real authentication and a confirmed tenant context underpin new product captures. Four optimized WebP images are published on the homepage; the feature page has been updated in German and English, both in content and design.

3D visualization

First 3D view for existing models and views

  • The spatial projection displays configured system shapes, groups and relations from existing model data. The 2D view remains available; 3D geometry is not persisted as a second source of model truth.

Scalability and measurement

Populated load profiles and deployment read phases checked

  • Single-tenant profiles, API timings and deployment read phases were measured and documented using actual data. Checks distinguish populated datasets from empty fixtures and make runtime contributions traceable.

Dashboard layout

Manual tile placement and saved sizes

  • Dashboards gained automatic and manual layouts with saved tile positions and sizes. Metrics, lists and other tile types remain connected to their underlying model and operational data.

Dashboarding

Dashboarding extended with source-aware filtering and precise per-item selection

  • Tile configuration now adapts selectors to active data sources and applies only relevant filters to metric computation.

Administration

Admin tool sharpened for operational steering and quality control

  • Governance, control, and intervention flows were consolidated to make admin operations faster and more consistent.

Product core

Instance views established as an operational core

  • The instance editor is now used daily and links model maintenance, relations, and visualization in one workflow.

Visualization

Visualization sharpened further for daily work

  • Visualization layout, readability, and interaction were refined again to accelerate business and operations work.

Website

Public website positioned as a product-focused one-pager

  • The website was reshaped into a professional one-pager with clear product blocks and stronger value messaging.

Administration

Admin tool expanded into its own product area

  • The admin tool became a central workspace for governance, quality checks, and operational interventions.

Documentation

Developer documentation established as a major workstream

  • Developer docs were structured, visually unified, and adopted as a reliable reference for engineering decisions.

Help system

Help system evolved into a consistent guidance layer

  • Help content evolved from isolated hints into consistent, role-oriented guidance for users and admins.

Method

Specialized skills introduced into the delivery workflow

  • Skills were introduced for recurring tasks to increase quality, delivery speed, and repeatability.

Permissions

Permission model with users and groups introduced

  • Permissions were implemented with user- and group-based controls to keep visibility and access decisions consistent.

Method

Test harnesses established for critical themes

  • Harnesses were established for visualization, relation logic, deployments, and permission edge cases.

Messaging

Messaging system integrated into the platform

  • A messaging system was integrated to provide structured communication and notification within the product context.

Method

Tooling selected through explicit decision criteria

  • Tool decisions were prioritized by measurable impact on product quality, automation, and operational reliability.

UI components

Footer component introduced as reusable base element

  • The footer component was introduced centrally to provide consistent navigation and context information across pages.

Visualization

Model relation and state visibility improved

  • Visualization became easier to read so domain relations and state transitions can be assessed faster.

Visualization

Visualization expanded for relations and filtering

  • Filtering, highlighting, and relation views were expanded so complex dependencies can be understood faster.

Deployments

Deployment transparency hardened for operations

  • Deployment lists and views clearly show recorded assignments and flagged problem cases.

Domain logic

System, delete, and ownership rules stabilized

  • Critical domain rules were unified so deletion paths, ownership behavior, and references stay consistent.

Test coverage

Test coverage raised as a quality metric

  • Coverage across core modules was raised substantially and adopted as an explicit quality indicator.

Project start

Started TOMATo app delivery with Pure GenAI

  • Delivery started with a clear product target, iterative feedback loops, and early template-first guardrails.

Key outcomes

  • Faster iteration from idea to production-ready change with explicit validation.
  • Fewer regressions through consistent type/lint/build checks on each change.
  • Higher transparency across instances, relations, and deployments through consistent view/edit paths.
  • More stable domain behavior across system boundaries through hardened ownership and delete rules.

Project start

2026-02-15

Back to home