Data room
Acquisition package
Enough information to evaluate the asset and buy it without a call. Complete source code, secrets, production dumps and credentials are never part of this public data room. They are released only through the private acquisition vault after cleared payment.
Technical details on this page come from the seller's documentation of the product. They are confirmed against the repository snapshot that is delivered in the vault.
Contents
What this data room covers
- Product overviewThis page and the product page.
- Feature inventoryModules table below.
- High-level architectureArchitecture section below.
- Component diagramArchitecture section below.
- Technical stackArchitecture section below, with its evidence status.
- Database and multi-tenant modelData model section below, no sensitive data.
- Roles and permissionsRoles table below.
- Deployment overviewDeployment section below.
- External services and dependenciesDependencies section below.
- LicencesDependencies section below.
- Exact asset list and exclusionsIncluded and excluded lists below.
- Transfer checklistTransfer section below.
- Acquisition FAQOn the main acquisition page.
- Acquisition agreement previewThe terms page.
Feature inventory
Modules and their evidence
| Module | What it covers | Evidence |
|---|---|---|
| Dashboard | Central operational view of the restaurant and access to the main workflows. | Visible in the demo |
| Recipes | Structured recipe management with food costing, linked to the items used in the kitchen. | Visible in the demo |
| Items | Management of the products and ingredients used in the operation: units, costs and stock thresholds. | Visible in the demo |
| Stock + OCR | Inventory workflows and assisted capture of information from documents through OCR. | Documented |
| Runs | Organisation and tracking of production runs and repeated work. | Visible in the demo |
| Reports | Reports and operational visibility across stock, waste, checklists and activity. | Visible in the demo |
| To-Do | Task management inside the restaurant environment. | Visible in the demo |
| Closeout | Structured, traceable end-of-day closing processes. | Visible in the demo |
| Events | Operational management tied to events and exceptional services. | Visible in the demo |
| Designs | Experimental visual and plating assistance, separate from the cost calculations. | Visible in the demo |
| Chat | Communication in context, inside the platform. | Documented |
| Restaurant selection / multi-tenant | Separation by company and restaurant, and the ability to operate several clients. | Visible in the demo |
| Global Admin | Central administration of the SaaS platform. | Documented |
"Visible in the demo" means the module appears in the demo environment's navigation or screenshots. "Documented" means it is described in the seller's product documentation.
Architecture
Components and stack
- Frontend
- React, TypeScript, Vite; routing and internationalisation.
- API
- Node.js, Express, TypeScript; REST.
- Data access
- Prisma ORM.
- Authentication
- JWT-based authentication with role-based permissions; company and restaurant access limit the records a user can reach.
- Hosting
- Hetzner (UnderStack's own infrastructure, not part of the transfer; the deployment configuration is).
Data model
Multi-tenant model, without data
The database schema and migrations are part of the acquisition. No production dump and no third-party personal data are included; the product can be delivered with an empty database and safe seed data.
- Company → Restaurant → UserRestaurantAccess
- The multi-location structure: a company has restaurants, and users are authorised for selected restaurants.
- Items → recipe ingredients → recipe and portion cost
- The cost foundation: item prices and units feed recipe costing.
- Recipes → Runs
- Production runs are executed from recipes.
- Stock + Waste + Runs + Tasks + Events + Closeout → Reports and Dashboard
- Operational records are the source of the management view.
Access
Roles and permissions
- Global Admin
- Administers the platform across companies.
- Admin
- Manages a company, its restaurants, users and access.
- Head Chef
- Coordinates preparation, costs, stock and follow-through.
- Sous Chef
- Runs kitchen execution day to day.
- Kitchen Helper
- Works the recipes, tasks and checklists assigned to them.
- Viewer
- Read-only access.
The action-by-role matrix is part of the technical documentation in the vault.
Deployment
Deployment overview
GastroApp runs today on UnderStack's infrastructure. The acquisition delivers the deployment configuration, a documented list of environment variables (names only, no secrets) and a deployment checklist, so the buyer can run it on their own accounts and hosting.
Dependencies
External services and licences
The full inventory of external services, relevant dependencies and their licences is compiled from the repository and delivered in the acquisition vault. Third-party software is not transferred as UnderStack property: each dependency keeps its own licence, and the buyer is responsible for complying with it.
Assets
Included and excluded
Included
- Source code repositories
- Database schema and migrations
- Tests and tooling
- Deployment configuration and guide
- Technical and functional documentation
- UI/UX and graphic assets
- GastroApp brand and brand assets
- Domain gastroapp.dk
- Commercial rights and transferable IP
- Migration guide and transfer checklist
- 30 days of asynchronous transition support
Not included
- The seller's personal accounts.
- UnderStack's general infrastructure used by other products.
- Secrets, keys and credentials that must not be transferred.
- Code or assets that belong to other UnderStack products.
- Third-party service accounts that cannot be transferred.
- Open-source or commercial dependencies, which keep their own licences.
- Future development that is not expressly part of the 30-day transition support.
Transfer
Transfer checklist
After payment, the vault opens with this checklist and the status of each item. Items marked as needing your action are the ones where you provide something.
- Source code repositoriesNeeds your action
- Database schema and migrations
- Tests and tooling
- Deployment configuration and guideNeeds your action
- Technical and functional documentation
- UI/UX and graphic assets
- GastroApp brand and brand assets
- Domain gastroapp.dkNeeds your action
- Commercial rights and transferable IP
- Migration guide and transfer checklist
- 30 days of asynchronous transition support
Private repositories are transferred through GitHub's official transfer or invitation so the history stays with the code. The domain moves through the registrar's normal process.
Agreement
Agreement preview
The acquisition agreement is shown in full on the terms page. You accept a specific version before any order is created, and the version and its hash are stored with the order.
The product already exists. Review it, buy it, make it yours.
€39,900 EUR, one time. You can complete the standard process without a meeting.