Custom software
for your customers.
Service portal
Customer project · Production app
In test → Live
- Requirements agreeddone
- Prototype delivereddone
- Feedback round 2in progress
- Go-liveplanned
Your customer. Your solution. Our platform.
You, the partner
- Customer relationship, contract and offer
- Consulting, requirements and concept
- Prototype and production app, built in Fleet
- Support and further development after go-live
NYO
- Fleet: console, workspace and portal
- The NYO Core as the foundation of every app
- A test and a production environment for every app
- Help with setup and operations
Your customer stays your customer
You sign the contract, you run the project, you are the contact – from the first meeting to support after go-live.
AI builds, you decide
An AI agent writes the code in an isolated environment. Your team decides what gets published and what goes live.
Only the core is fixed
Sign-in with two-factor, roles and permissions, lists with search and filters, Excel export, attachments and an API come with every app. You only build what sets your customer's business apart.
For IT service providers, system houses, consultancies and agencies who want to offer custom software to their customers.
One place for your projects. One core for every app.
Console
Your workplace: customers, apps, planning, milestones, feedback and documentation in one place – and for every app its own workspace where it is built. What you create is not visible to other partners.
Portal
Your customers' window into the project. Per app, a dedicated access for their contacts, with milestones, feedback, open questions and published documentation.
Core
The technical foundation of every Fleet app: an API core and a frontend core. New apps are generated on it right inside Fleet – prototype and production app share the same foundation.
From the first meeting to the app in production.
- 01
Create customer and app
Your team creates the customer and their app in the console and invites their contacts to the portal. From day one they see the project plan there.
- 02
Plan and approve
In planning, Claude reads your customer's documents and proposes requirements, milestones, interfaces and open questions. You accept or discard – Fleet prices the effort at your rates, and your customer approves the scope with its hours and amount in the portal. You write your offer yourself, as always.
- 03
Build and show the prototype
In the workspace the AI agent builds the prototype on the NYO Core. In the customer meeting you share it live, and your customer gives feedback in the portal – round after round.
- 04
Make it production-ready
The prototype becomes the app for real use: interfaces, taking over existing data, tests and permissions – what only this project needs. Your customer tries every version on the test environment.
- 05
Go live
Every published version runs in the test environment first. Going live takes exactly that version into production – with its own database and its own keys.
- after
Support and evolve
Your customer reports wishes and bugs in the portal, you implement them in the workspace. Fleet checks every app once a minute and reports an outage to everyone looking after it.
How long a project takes depends on its scope – the process stays the same.
Your customer has already built a prototype with their AI? Even better – it becomes the spec.Show, don't tell. The prototype runs live.
Stock
- In stock
- Reorder
- In stock
Share live session
Anyone with the link sees this dev preview live and without a Fleet account, including every change the agent makes. Only for this app, and only until the session ends.
Duration
No account
Your customer needs no access to Fleet. The link is enough – in the browser, on a phone too.
Time-boxed
1, 2, 4 or 8 hours, for this one app only. After that the link stops working.
End it any time
One click on “End”, and the link stops working.
Build apps – right inside Fleet.
Service portal · Workspace
Preview runningPlease build this feedback:
#12 Filter by status- Read feedback #12
- Changed 3 files
- Updated the preview
The order list can now be filtered by status – have a look in the preview.
Orders
- Open
- Open
- Open
- Open
New app on the NYO Core
A new app is generated straight from the console – with sign-in, permissions and administration from the first commit.
Built in conversation
Your team describes what the app should do. An AI agent based on Claude writes the code, starts the app and reads its logs.
Knows the project
A # pulls feedback, milestones and documents right into the conversation. The agent reads along – and every session stays linked to the ticket it was about.
Live preview
The app runs while it is built: with an address bar, back and forward, and tablet or phone views. Every app has its own, unguessable preview address.
Changes at a glance
Everything not yet published is listed in the “Changes” tab – with history and discarding of single files. Publishing is a commit with its own message to the repository.
Isolated and traceable
The agent works in an isolated sandbox that reaches the internet only through an allowlist. Every run is recorded with its usage per app and customer.
Everyone builds a prototype today. You turn it into software.
Your customer's prototype
built with their AI
Shows what the app does
- Screens and navigation
- Flows from start to finish
- Rules and calculations
- Data and fields
The app
on the NYO Core
Brings what a prototype lacks
- Login, MFA and permissions
- A real database with migrations
- Change history and export
- Operations with test and production environments
- 01
Upload the prototype
In planning you upload your customer's prototype under “Customer prototype” – the project folder as a ZIP or a single file, whatever AI built it. Credentials, keys and databases stay out.
- 02
Rebuild on the NYO Core
In the workspace the AI agent rebuilds the app on the NYO Core – screen by screen, rule by rule. Sign-in, permissions and administration come from the core, not from the prototype.
- 03
Compare and accept
The new app is compared with the prototype until it does everything the prototype did. Your customer follows every step in the portal and gives feedback right there.
The prototype never becomes part of the app – it is the template, not its code.
What a prototype doesn't show – interfaces and data migration – planning proposes as items of their own.
This works today.
Project tracking
Every app with status, owners and progress. Customers, apps and contacts in one place – visible to your whole team.
Milestones
A milestone plan per app, with dependencies and dates. Your customer sees the same plan in the portal as your team.
Feedback
Your customers report feedback right in the portal, with screenshots and comments. Your team works through it on a board – with status, labels and assignees – and implements it in the workspace.
Documentation
Migration, interface and requirements documentation with status, approval and change history. Your customer confirms requirements right in the portal.
Customer portal
Per app, a dedicated access for your customer's contacts, protected by link or sign-in. Milestones, feedback, open questions and documentation – nothing to install.
Own app, own data
Every app runs on its own – with its own database and keys, separate for test and production. Production gets exactly the version you tested.
One licence for your team. A fixed price per app.
Base fee
Fleet licence
Your team manages customers and apps, builds with the AI agent and gives your customers a portal of their own.
€499per month · net
Included
- Any number of team members, no price per user
- Console: customers, projects and apps in one place
- Workspace with the AI agent, each team member with their own Claude access
- Customer portal with preview, milestones, feedback, approvals and documentation
- Project control and an operations overview across all apps
- Upkeep and further development of the platform
- 1 hour of partner support per month
Plus a price per app
You choose a class for each app. The price follows the resources an app needs, not the number of screens, features or users.
Small
App class€49per app and month
For small applications and single processes that need few resources.
Typical: leave requests or an inspection log for one team
- Computing power
- 1 vCPU
- Memory
- 2 GB
- Storage
- 10 GB
Medium
App class€99per app and month
For applications in regular use that need more capacity.
Typical: a customer portal in daily use
- Computing power
- 2 vCPU
- Memory
- 4 GB
- Storage
- 30 GB
Large
App class€199per app and month
For resource-intensive applications with large storage and computing needs.
Typical: a platform with many documents, images and reports
- Computing power
- 4 vCPU
- Memory
- 8 GB
- Storage
- 100 GB
Resources per environment
The values shown apply from the moment an app is created in NYO Fleet (the price covers the test and the production environment). They are a guide for choosing the right app class. We reserve the right to change resources and performance limits and will announce any change in good time.
Included in every app
- Provisioning in the NYO Cloud
- Computing power, database and file storage within the class
- The NYO Core: sign-in with two-factor authentication, roles and permissions, lists with search, exports and an API
- Hosting, operations, monitoring and backups
- Operation from development through test to live
In development an app costs as much as a live app.
The fee starts when you create the app. Going live adds nothing.
Worked example
What does Fleet cost you per month? Set how many apps you run in each class.
Small
€49 per app
Medium
€99 per app
Large
€199 per app
Fleet licence€499
2 × Small€98
1 × Medium€99
Per month, net€696
Claude isn't included. You pay for it through your own plan.
When an app grows
When an app's resource needs grow, we let you know in good time. If its load stays higher, the matching class becomes necessary.
- 01
Choose a class
When you create an app, you choose Small, Medium or Large and see its limits and price up front.
- 02
Usage in view
Fleet measures what the app actually uses: computing power, memory, database and files.
- 03
Notice in good time
When an app nears the limit of its class, Fleet tells you before things get tight.
- 04
Upgrade when needed
As soon as an app permanently needs more resources than its booked class provides, it moves up to the matching class after prior notice. That keeps operations reliable and billing fair.
Only in the NYO Cloud
We run and maintain the NYO Core centrally. An installation on your own servers or at your customer's site isn't possible.
Not included
You pay for Claude through your own plan. The support hour covers questions about Fleet, not the development of your customers' apps. Special services and infrastructure beyond the booked class aren't included either.
All prices are monthly and net, plus statutory VAT.
What changed recently.
Become a partner
Become a partner.
We guide your start in person – and show you Fleet on a real project first.
Your contact

Marco Ertelt
Sales Manager · NYO GmbH
Or book a meeting right away.
Book a meeting on Calendly