The tools your company needs live in Excel files and in an IT backlog that never gets shorter. On Kinster your business department describes the app in plain language, the assistant builds it in the browser, and needful-apps reviews every app before go-live. Login, database, deployments, backups, monitoring, AI, dictation, email and SMS are already in there. Hosted in a German data centre or on your own server.
This is Kinster: here you create professional applications by describing them. They fit your corporate design and are protected against unauthorised access.
The workshop needs a tool loan list, so it creates one itself: a name, who may use it, and one sentence about what it should do.
Here you describe instead of code. She says what is missing, the assistant builds it and writes down what it changed. If you prefer, you dictate.
Need help? Ask for a review. Once it is done, it goes for approval. From here the platform takes over.
Kinster runs the pre-check: secrets in the code, database access rules, logs without personal data. Plus tests that click their own way through the application.
needful-apps does the final human review and releases the application. Nothing goes into production unreviewed.
And this is what it looks like when the workshop opens it. Photos instead of part numbers, overdue returns at the top, with the number of days.
The rule from earlier holds: a return more than fourteen days out is refused. Checked in the backend, not in the browser. What comes back is counted down at once.
Kinster by needful-apps. Your department describes the app. By this afternoon, it is running.
Every business department knows its processes best, and every one of them has a list of tools it has needed for years: shift planning, test data collection, leave requests. IT cannot keep up, new developers are nowhere to be found, and so shadow IT grows: spreadsheets with macros that three departments end up depending on, without permissions, backups or tests. Kinster gives that energy a safe place: the department builds it themselves, AI-assisted and faster than ever in Excel, while the platform's guardrails, automated checks and reviews turn it into reliable software instead of new sprawl.
A new app starts with a form: a name, who may see it (groups picked from a list, from your own team to a customer group), and one sentence about what it should do. Kinster turns that into a ready-made project: backend, frontend, database wiring and the working instructions for the AI assistant. From there it continues in a chat: the department describes in plain language what the app should do, the assistant implements it in the project, inside the guardrails the platform sets. Anyone who prefers to look at the code opens VS Code in the browser right next to it.
The text grows as you talk, a level meter shows whether the microphone hears you at all, and nothing is sent until it reads right. Transcription runs at a European provider, where the recording is neither used for training nor kept afterwards.
No provider contract, no key, no second invoice: Kinster brings the access along. The assistant understands text and images, so you can attach a PDF, a screenshot or a sketch, and the platform decides per request what is needed. It draws on a credit whose balance sits in the dashboard.
The development environment runs on the server and opens in the browser, with a pre-connected test database, Git and an AI assistant in the terminal. No setup on the workstations, no admin rights required.
"Start test" builds the app and serves it under its own preview address, with database migrations applied automatically. Colleagues can take a look right away, before anything goes live.
Icons and illustrations are generated by the AI assistant on request and stored right in the project. No stock photo hunt, no licensing questions, no detour through graphics tools.
The app template sets the rules the AI assistant reads along: business logic belongs in the backend, data access needs row-level rules, interfaces are bilingual. The result is uniform, maintainable software instead of ten styles.
The images above show the workshop. This is what comes out of it: a viability calculator for photovoltaics with storage and a wallbox, built on Kinster in four rounds of conversation totalling about 45 minutes. It was described in plain language, the assistant built it, and the platform checked it. The recording shows the last of those four rounds.
Two things about it matter more than the looks. First, the entire calculation runs in the backend: there is not a single formula and not a single figure in the browser, not even for the charts. Anyone reading the page source finds nothing that could be tampered with. Second, every assumption comes from the database rather than from the code, each with a source and a date, and they can be changed in the interface. A changed assumption recalculates immediately.
None of this is a happy accident; it is what the platform requires. It is exactly what the review looks for and what the automated checks verify before every approval. The calculator is bilingual, has access rules on every table and brings its own interface tests, which run on every approval request. Nobody had to ask for any of it.
And the note under the result, saying these are guide values and not financial advice, belongs to the same attitude: an app that calculates with money says what it is based on.
A finished app does not stop at input field and table. It may ask the AI, send an email and send an SMS to a mobile phone, without your company signing contracts or managing keys: Kinster brings the access to the providers, and you pay for what is used. Each of these functions is off by default and enabled per app, so nothing starts up that nobody asked for.
Classify a piece of feedback, summarise a long text, draft an answer: the app asks the AI during normal operation, for the people who use it. With hard limits: this AI writes no program code and answers no questions about IT security. Requests of that kind are rejected by the platform before they reach the provider.
The app sends an SMS through a European delivery service. The sender is fixed, only the country codes you allow are accepted, and an hourly limit slows down any app that runs away with itself.
Mail goes through your own mailbox, connected centrally instead of wired up again for every app. It is enabled per app and recorded in the audit log, so nobody writes in the name of the company unnoticed.
AI, SMS and review hours each have their own credit. A traffic light shows how long it will last, topping up is requested, and whatever is empty slows down only itself. Costs without cover do not arise.
AI, speech recognition and SMS delivery run at providers in France, Denmark and Germany. Your input is not used for training there, and on our side only the billing record of a request remains, never its content.
With Kinster, AI-generated code never goes live unchecked. Automated checks block broken versions at submission, then needful-apps reviews every app and every major update. Only after approval does it deploy: without interruption, with one-click rollback.
Secret scan, dependency audit, CVE scan of the container images and database migrations with mandatory access rules. What fails cannot even be submitted.
The assistant writes interface tests for every app: fill in the form, submit it, check that the right thing comes out. They run automatically on every approval request, in the interface language, with a video recording for failures.
If you are unsure, ask for a review without submitting. That costs less time than an approval round that fails at the same spot.
Every new app and every major update is reviewed by us before go-live: architecture, security, data access. Questions travel as a comment thread with screenshots right on the app, with email notifications.
Deployments run without interruption; the previous version stays ready. If something goes wrong, one click brings back the last working version, deployment history included.
Review time runs against an hours quota you can inspect in the dashboard: a review timer per task, usage and remainder visible at any time, top-ups on request. No surprises on the invoice.
The first question after every successful internal app is: can our customers see this too? That is what invitations are for, instead of shared accounts. Single use, with an expiry date, and whoever comes in through one has to set up a second factor. The account itself can carry an expiry date as well: when the project ends, so does the access, without anyone having to remember. All of it is managed in Kinster, not in an administration tool only IT can operate.
Sign-in via single sign-on with the existing account. When somebody leaves, access to every app ends at the same moment, because it hangs on a single place.
For each person you can see which apps they reach, through which group, and what has been released to them directly. A single app can be released to a single person without inventing a group for it.
Only those who should develop may develop, and per app you can name the group allowed to work on it. Anyone else does not see the app, neither in the list nor via its address. Access to the finished apps is untouched by this.
Store your company's logo, colours and specifications once, centrally in the settings. Every new app starts in your corporate design without anyone looking up colour codes: the AI assistant reads the specification and builds the interface accordingly. If the design changes later, the platform offers each app the update, while deliberate deviations of individual apps are preserved.
Logo, icon mark, background image, font and colour specification in one place. The platform's sign-in page carries your design too.
For every colour, Kinster immediately checks the WCAG contrast: if a surface cannot carry readable text, the system warns before the colour ever lands in an app. Essential for anyone supplying the public sector.
For each file you decide whether it may be copied into app projects. A corporate font without a webfont licence automatically stays out instead of ending up in ten repositories.
Building an app is the smaller part. Running it safely for years is the bigger one, and that is exactly what Kinster takes off your hands. Hosting is no exception: on request, needful-apps provides and operates the entire environment in a German data centre, the all-inclusive package with no servers of your own. If you prefer your own infrastructure, Kinster runs there instead, with the same feature set and the same level of care.
Nightly backups of databases, configuration and app code, every file verified after creation, then shipped off-site tamper-proof: the server may write backups but never delete them. Ransomware hits a wall.
Every week the platform automatically restores a backup into a throwaway database and verifies the result. A backup that has never been restored is not one; the result shows up in the dashboard.
The admin installs platform updates from the dashboard, with progress display. The licence renews itself, certificates are renewed by the platform, and daily housekeeping clears out old containers.
Every app is monitored from the outside, outages trigger email alerts. The dashboard shows status, response times, logs and container health of all services.
Running apps are continuously checked for known vulnerabilities. Findings show up right on the app tile and detail page, with severity.
Employees sign in via single sign-on with their company account, customers and prospects with email, password and MFA. Groups control per app who sees it: managed centrally, no per-app logins, no shared passwords.
Every approved app automatically appears in your employees' portal, with icon, description and version.
Every app automatically gets its tables in a database on your server, with row-level access rules and versioned migrations. No separate database project.
Dashboard, app pages and assistant are built for small screens: look at an approval on the move, read the conversation, answer a question, without opening the laptop.
At the next sign-in, once, not on every visit. Anyone who missed two jumps gets to see both.
An immutable audit log of every action: who changed, approved or deployed what. Important for certifications and internal audits.
Kinster is not a tool we hand over and leave: needful-apps sets up the platform on our infrastructure or yours, migrates existing tools, trains your departments and stays responsible afterwards: server maintenance, monitoring, backups and the code review of every new app, with agreed response times.
You keep control: your data, your code, and your own server if you want one. We make sure it turns into reliable software.
More background in our articles Ending shadow IT: from Excel sprawl to an internal app platform and Vibe coding in the enterprise: why AI-generated code needs a review.
Kinster is an app platform for companies: one central, protected entry point through which employees, customers and prospects access your web apps. For every app you decide granularly who sees it: just your own team, individual customer groups or everyone. Business departments build new apps AI-assisted right in the browser and take them live through a defined review process. needful-apps operates the platform and reviews every app before go-live.
No. Every new app starts from a template with a ready-made project structure, database wiring and working instructions for the AI assistant. Development happens in a chat: the department describes in plain language what the app should do, the AI implements it within the guardrails, and every change can be undone with one click. Anyone who wants to work in the code opens VS Code in the browser right next to it. Onboarding training is part of the offer.
Guardrails instead of trust: twelve automated checks run on submission and block versions that fail, a thirteenth pulls in the CI result afterwards (among them a secret scan, dependency audit, CVE scan of the containers, database migrations with mandatory access rules and a search for personal data in the logs). On top of that come interface tests the assistant writes itself, which run automatically on every approval request. Then needful-apps reviews every app and every major update before it goes to production. Business logic always lives in the backend, never in browser code.
Through invitations instead of shared accounts: single use, with an expiry date, and whoever comes in that way has to set up a second factor. The account itself can carry an expiry date too, so a project login ends on its own. For each person you can see which apps they reach and through which group; a single app can also be released directly to a single person. All of it is managed in the Kinster dashboard.
Kinster brings it along. The access to the AI provider sits with needful-apps, so you need neither a contract of your own nor a key nor a second invoice. The assistant understands text and images, PDFs and screenshots can be attached directly, and the platform decides per request which model is needed. You pay for what is used, from a credit whose balance and history sit in the dashboard; topping up is requested, never booked quietly. Anyone who prefers their own AI access can store it per person. Processing runs at a provider in France, and your input is not used for training there.
Yes. An app may ask the AI during normal operation, for instance to classify a piece of feedback, summarise a long text or draft an answer. This is off by default and enabled per app, with its own credit, separate from the review hours and from the assistant credit. The limits are drawn hard: this AI writes no program code and answers no questions about IT security, and requests of that kind are rejected before they reach the provider. On top of that come volume limits per app and hour.
Yes, through a delivery service in Denmark, connected by the same central route as the AI. This too is off by default and enabled per app, with its own credit. Per installation we set which country codes are allowed (Germany by default), optionally a fixed sender and an upper limit per app and hour. Numbers without a country code are rejected rather than guessed, and the recipient number does not appear in our logs.
Yes, through a central connection to your own mailbox rather than a third-party mail sender. Sending is enabled per app, with an hourly limit, and every activation is recorded in the audit log.
Via single sign-on: employees use single sign-on with their existing company account, customers and prospects register with email and password plus multi-factor authentication. Groups control per app who sees it: managed centrally, no per-app logins.
Either with needful-apps or on your own server, in both cases in a German data center, operated with Docker Compose, no US cloud. The AI, speech and SMS services Kinster brings along also run at European providers (France, Denmark, Germany) which do not use your input for training; on our side only the billing record of a request remains, never its content. The source code of every app lives under version control on the server of the installation and is mirrored into your own Git hosting on request; data lives in a Supabase database of the installation. Daily backups are stored tamper-proof (append-only) and regularly tested for restorability.
No. Kinster is available as a complete package: needful-apps provides the servers in a German data center, operates the platform and keeps it up to date, while you and your departments only need a browser. If you have your own infrastructure or your own requirements, Kinster runs on your own server instead; feature set and care are identical, and a later move is possible in both directions.
Deployments run without interruption (zero downtime); if something goes wrong, one click rolls back to the previous version. Monitoring checks every app from the outside, alerts go out by email, and the dashboard shows status, logs and deployment history for every app.
Yes, automatically. You store logo, colours and design specifications once, centrally in the settings; every new app starts in your corporate design, and the AI assistant applies the specification when building the interface. Kinster also checks every colour for sufficient WCAG contrast, which matters especially for suppliers to the public sector. If the design changes, the platform offers each app the update.
Yes. Existing applications move onto the platform, including user accounts and access; grown Excel or Access solutions are rebuilt as proper apps, with permissions, backups and history. needful-apps handles the migration as part of the setup.
Kinster consists of setup, license and ongoing care (server maintenance, monitoring, code review, response times per agreement). Review hours are transparently visible in the dashboard. Pricing depends on scope and number of users, and you get a transparent quote in a free initial consultation.
