iiterate Technologies iiterate Technologies
Deutsch
Contact us

Software development

Software development and AI development from Rhineland-Palatinate

iiterate Technologies builds AI applications and custom software, from architecture through delivery to operation, on your own infrastructure or in EU hosting. Here are our guides for taking a prototype into production and pages on the regions from the Ahr to Hamburg.

From Prototype to Production

A prototype shows that an idea holds up. The series covers what sits between “works on my machine” and “works in the business”: security, handover, operation, the legal frame and choosing the right support.

Overview and checklist From prototype to a production-ready application A prototype answers one question: does the idea even work? An application an organisation relies on day to day has to answer seven more, questions nobody had to ask while it was still a prototype. Each one comes with its typical default setting and a check step for assessing where things actually stand. Go to the overview
  1. 01 Built with Lovable, Bolt or Replit: what is likely still open Row-level security, CVE-2025-48757, frontend keys, migrations: what is typically still open in Lovable, Bolt or Replit apps, and how to check it directly.
  2. 02 What studies show about the quality of AI-generated code Veracode, GitClear, DORA and METR: what the most cited studies actually measure about the security, maintainability and speed of AI-generated code.
  3. 03 Spotting technical debt in AI-generated code Six types of technical debt typical in AI-generated code: how even non-developers can spot them, and which cost drivers each one creates.
  4. 04 The business unit built an app: what IT checks before taking it over A business-unit app is heading into production: which points IT settles before approval, which can follow later, and how a handover document is built.
  5. 05 From proof of concept to routine operation: the technical handover What a proof of concept needs before routine operation: six handover artefacts, and the difference between working and operable.
  6. 06 How accurate can a software estimate be? The estimation range Why an early software estimate is a range, which milestones narrow the estimation range, and when a fixed commitment becomes justified.
  7. 07 Running an application in-house: what day-to-day operations involve What running an application in-house involves, from monitoring to recovery, and when managed operation or a platform fits better.
  8. 08 From an n8n workflow or Streamlit script to an operable application When an n8n workflow or a Streamlit script is enough in production, what it lacks, and what to port or keep in the tool when moving it over.
  9. 09 Approving AI tools in the development team: which guardrails are needed The guardrails a team needs for Claude Code, Cursor or GitHub Copilot: permissions, review before merging, secrets, customer data and code provenance.
  10. 10 Who is liable when AI-generated code causes damage? Product liability for software, Cyber Resilience Act reporting duties, AI Act Article 50 and NIS2: the rules that apply to AI-generated code in 2026.
  11. 11 Does AI in an application need to be labelled? What Article 50 of the EU AI Act has required since August 2026, who counts as provider or deployer, and what labelling looks like in small applications.

Regions (German)

These regional pages are in German. They describe the regional economy from the Eifel to Hamburg and the software and AI work typical there. Close to Adenau and Remagen, on-site collaboration is realistic; with teams further away, we work mostly remotely.

  1. Landkreis Ahrweiler Ahr, Adenau und Nürburgring Adenau, Nürburg, Meuspath, Grafschaft, Altenahr, Dernau, Ahrbrück
  2. Landkreis Mayen-Koblenz, Landkreis Neuwied, Landkreis Ahrweiler Mittelrhein: Andernach, Linz, Bad Breisig und Mendig Andernach, Linz am Rhein, Bad Breisig, Brohl-Lützing, Mendig
  3. Landkreis Vulkaneifel, Landkreis Cochem-Zell Vulkaneifel und Ulmen: Daun, Gerolstein, Ulmen, Kelberg Daun, Gerolstein, Ulmen, Kelberg
  4. Eifelkreis Bitburg-Prüm, Landkreis Bernkastel-Wittlich, Landkreis Cochem-Zell Eifel und Mosel: Bitburg, Prüm, Wittlich, Cochem Bitburg, Prüm, Wittlich, Cochem
  5. Landkreis Vulkaneifel, Landkreis Bernkastel-Wittlich, Eifelkreis Bitburg-Prüm, Landkreis Cochem-Zell Landkreise im westlichen Rheinland-Pfalz Daun, Wittlich, Bitburg, Cochem, Morbach, Kaisersesch
  6. kreisfreie Stadt Mainz, kreisfreie Stadt Trier, kreisfreie Stadt Ludwigshafen am Rhein, kreisfreie Stadt Kaiserslautern, kreisfreie Stadt Worms, kreisfreie Stadt Speyer Städte in Rheinland-Pfalz: Mainz, Trier, Ludwigshafen, Kaiserslautern, Worms und Speyer Mainz, Trier, Ludwigshafen am Rhein, Kaiserslautern, Worms, Speyer

If the question is still whether and where AI makes sense for your company, start with KI-Beratung. Fundamentals on AI in knowledge management are under Knowledge.

Let us talk about your project

Whether it is a prototype, an internal tool or an AI application: describe briefly what you are building or want to take into production.

Get in touch See the service Or: request a 20-minute first call

Arthur C. Clarke

“Any sufficiently advanced technology is indistinguishable from magic.”