New applications
From the first screens and data design to the backend, interfaces and deployment. We regularly show features in a working application so you can check that it does what you need.
We build business systems, web and mobile applications, and software for devices. We also take over projects already in progress. Our developers use AI assistants and agents; our team handles design, code review and deployment.
We can take on the whole development effort or join your team. We build on what already works and plan gradual modernisation. We select the first useful increment by its benefits, costs and dependencies, so you do not have to fund the whole scope at once.
From the first screens and data design to the backend, interfaces and deployment. We regularly show features in a working application so you can check that it does what you need.
We review the code, dependencies, tests and deployment process. We identify obstacles and suggest which fixes and changes to tackle first. For an unfinished project, we start by finding what prevents completion.
We connect the application to ERP, CRM, sign-in and other services through APIs or messaging. We also handle outages and retries so that a failure in one system does not lose data between the others.
Searching company documents, processing invoices or drafting customer replies. We connect AI to your data and permissions and evaluate how well it works on real tasks.
We develop for iOS and Android. We choose native or shared code based on the application's features, device integration and how you plan to maintain it.
We write C/C++ software for devices and their controllers. Our experience includes robots, IoT and payment terminals, where the application must work with the behaviour of real hardware.
We use AI to understand code and prepare changes, tests and documentation. We work with GitHub Copilot and Claude Code, and assign whole development tasks to agents. We draw on our own experience when introducing these practices to customers.
How we introduce AI to development teamsWe give it rules and context: architecture, business rules, testing practices and data access restrictions. We maintain these instructions as the project changes.
A developer reviews the design and code, checks tests and verifies application behaviour. A person who understands the project is responsible for accepting the change.
We compare time, defects and costs on similar tasks. We include reviewing and correcting outputs, because that work is part of the actual cost of development.
We agree the team and scope to suit the project. From the start, you will know who is responsible for each part and how we will check progress.
We clarify users, main tasks and connections to other systems. For an existing application, we examine the code and operations. We identify priorities and open questions.
We agree the scope, architecture, technologies and how to verify the result. We test uncertain integrations or requirements early. We prepare an estimate and work plan.
We deliver in smaller parts, review completed features together and incorporate feedback. We include tests and security checks in automated builds and deployment.
We prepare operations, monitoring, documentation and training. You own the code. We agree further development and support, or hand over management to your team.
Click a specific page element and add a comment. Your team can reply and mark feedback as resolved. No widget needs to be added to the website under review, and you can host the tool yourself.

Controller firmware, the Controls application for photography studios, and Access Server for robot records and management.
What we did for PhotoRobotGeocentrum for address processing, automated parcel measurement and a tool for comparing changes to the distribution network.
What we did for Packeta PPF a.s.Processing email attachments, reading invoices with AI and adding information from accounting history for subsequent approval.
What we did for PPFTell us who the application is for and what you already have. We will discuss where we can help.
Tell us what costs you the most time, money or operational effort. Together, we will choose a first step and a way to measure its benefits.
info@cloudfield.czThe site does not work without strictly necessary cookies, so those are always on. Traffic and LinkedIn campaign measurement only switch on with your consent. Rejecting is as easy as allowing – no hard feelings. Privacy policy
The site does not work without them. We set just one, and it remembers what you chose in this banner.
cf_consent · cloudfield.cz · 1 year — Stores your cookie settings choice.Google Analytics shows us how many people visit the site and what they read. It does not tell us who you are.
_ga · Google · 2 years — Distinguishes visitors for traffic statistics._ga_2FE6EFFNHT · Google · 2 years — Keeps session state for Google Analytics 4.The LinkedIn Insight Tag measures whether our LinkedIn campaigns are any good. LinkedIn may link the visit to your profile while doing so.
li_sugr · LinkedIn · 3 months — Probabilistic browser identifier for campaign measurement.bcookie · LinkedIn · 1 year — Identifies the browser for LinkedIn services.lidc · LinkedIn · 1 day — Routes requests to LinkedIn's servers.UserMatchHistory · LinkedIn · 30 days — Syncs identifiers for LinkedIn advertising.AnalyticsSyncHistory · LinkedIn · 30 days — Time of the last sync with the lms_analytics cookie.li_fat_id · LinkedIn · 30 days — Attributes a site visit to a click on a LinkedIn ad.