Sometimes the most interesting developments stem from decisions made decades ago. When I first started working with FileMaker 2.1 in 1994, I had no idea that it would turn into a journey through the world of software development spanning more than 30 years. Back then, FileMaker was still a relatively simple database program. My first applications were modest, but I was immediately hooked. Finally, it was possible to bring your own ideas to life, organize data, and develop applications without having studied computer science.
Over the following decades, this gave rise to numerous projects, customer solutions, and ultimately gFM-Business—a complete ERP system with CRM, Invoice, Inventory Management, Project management and many other modules. Over the years, thousands of fields, hundreds of processes, and countless business workflows have been modeled and documented.
Today, however, we have reached a point where software development is once again undergoing a fundamental transformation. This time, the catalyst is not a new Database, a new programming language, or a new operating system. The catalyst is artificial intelligence.
Why Software Development Is Undergoing Fundamental Changes Right Now
Many discussions about AI revolve around text, images, or chatbots. For developers, however, the real revolution lies elsewhere.
For the first time in the history of software development, it is possible to discuss architecture, data structures, user interfaces, and business processes with an AI system on an equal footing. The AI not only generates code but is also increasingly able to understand relationships, rules, and concepts.
This shifts the focus of development. In the past, a large part of the work involved implementing technical details. Today, it is becoming increasingly important to define the right structures, rules, and goals. The implementation can then be automated to a significant extent.
This opens up new possibilities, especially for developers with many years of experience. Knowledge that used to exist solely in a developer’s mind can now be documented, structured, and made usable through AI.
This article is not intended to be a traditional product announcement. SchallOS is currently in an active development phase. Many components already exist, while others are being developed step by step. The interesting part, therefore, is not the finished product, but the journey toward it.
For the first time in many years, a platform is emerging that doesn’t simply copy existing concepts, but consciously seeks to combine expertise built up over decades with the capabilities of modern AI systems. This isn’t about discarding what has been proven to work. On the contrary. The central question is:
How can we carry over existing solutions, knowledge, and experience into a new generation of technology?
Why Now Is the Right Time for New Platforms
The past few decades have been marked by increasingly powerful systems. At the same time, many development environments have become more complex. Cloud services, interfaces, security requirements, deployment processes, and integrations mean that even relatively simple applications are often much more complex to implement today than they used to be.
At the same time, AI offers possibilities that would have been unthinkable just a few years ago. This creates a window of opportunity that likely occurs only rarely in this form. Existing systems continue to function reliably. At the same time, entirely new tools are emerging that enable a different approach to software development.
Right at this Interface The SchallOS Business operating system is currently under development. It is not intended to replace existing systems, but rather to combine the strengths of traditional rapid development systems with modern web technologies, AI support, and a new architecture.
The Problem with Today's Business Applications
Most successful business applications are not developed in a single year. They evolve over many years. New requirements are added, customer requests are implemented, legal requirements change, and technological advancements make enhancements necessary. The result is often systems with an impressive range of features.
At the same time, however, complexity is on the rise. Many companies today rely on solutions that have evolved over the course of years or even decades. Often, in-depth knowledge of processes and interrelationships is held by only a few individuals. It takes new developers a long time to get up to speed. As a result, making changes is becoming increasingly difficult.
This is not a flaw in the original systems. It is a natural consequence of long-term development.
More and more interfaces
Today, modern business applications rarely stand alone. They communicate with online stores, accounting systems, shipping providers, banks, AI services, CRM systems, and numerous other platforms.
Every additional interface creates new possibilities. At the same time, it increases the maintenance burden. API versions change. Providers modify their services. Security standards are updated. What was originally a simple application gradually becomes a complex one Network of dependencies.
Many developers now spend more time on integration and maintenance than on actual development.
Increasing Cloud Complexity
Cloud services undoubtedly offer many advantages. At the same time, they often involve a level of technical complexity that is difficult for small and medium-sized businesses to grasp.
Server, Certificates, hosting, containerization, user management, monitoring, and security policies are important topics. However, they also create a significant administrative burden.
Today, many companies want one thing above all else: a solution that works. Not every user wants to deal with technical details. Many want to focus on their actual business processes.
Maintenance Instead of Innovation
Another problem with many established systems is that an ever-increasing portion of development time is spent on maintenance. Bug fixes, adjustments, and technical updates are necessary. At the same time, there is less and less room for true innovation. Many developers are familiar with the feeling of having good ideas but lacking the time to implement them consistently.
For the first time, AI is noticeably changing this balance. When part of the technical implementation can be automated, it creates new opportunities for architecture, creativity, and new concepts.
Why Traditional Script Logic Has Its Limits
Many development platforms are still based on concepts that originated decades ago. Scripts are called. Triggers respond to events. Menus are built. User interfaces are composed of many individual objects.
These approaches work. The question, however, is whether they will still be the most efficient way to proceed in the future. If AI is now capable of understanding business rules, analyzing relationships, and generating complex components, a new way of thinking will inevitably emerge.
Instead of linking hundreds of individual objects and numerous scripts together, a few intelligent components could handle most of the functionality in the future.
This is exactly where the development of SchallOS comes in. Not because existing concepts are wrong, but because new tools now open up different possibilities.
20 % Discount through July 31.
Valid for New purchases, Upgrades and future
gFM-NEXT and SchallOS projects.
How AI Is Really Changing Things for Developers
When people talk about artificial intelligence today, many first think of chatbots, automatic translation, or image generation. For developers, however, the real revolution lies elsewhere.
AI isn't just changing the pace of software development. It's changing the How software is created in the first place. In the past, almost every new feature started with technical work. You had to create tables, define fields, write scripts, build user interfaces, and tie countless details together. Even small changes could take a surprising amount of time.
Today, a developer can explain to an AI what they want to achieve. The AI then takes care of a large part of the technical implementation. This does not make the developer redundant. Rather, their role shifts from that of a mere implementer to that of an architect and decision-maker.
The real challenge is no longer writing code. The challenge is developing the right structures and making the right decisions.
Why Experience Is Suddenly Becoming More Important
An interesting side effect of the AI revolution is often overlooked. Many people assume that artificial intelligence devalues experience. In practice, however, I am currently observing exactly the opposite. The more experience someone has, the better they can take advantage of the capabilities of modern AI systems.
Anyone who has been working in a particular field for twenty or thirty years is familiar with the typical problems, the weaknesses of existing systems, and the needs of users. Today, for the first time, this knowledge can be directly incorporated into the development of new solutions.
AI does not replace this knowledge. It enhances it. This creates a situation that has rarely existed in this form before. Expertise built up over decades can suddenly be put into practice at a pace that would previously have required entire teams of developers.
Semantic Layers Instead of Cryptic Logic
Another important point concerns the understandability of software. Many systems consist of thousands of technical details. Variables, scripts, triggers, and special cases grow over the years into complex structures. It often takes new developers months to fully understand how everything fits together.
That is why the semantic level will play a much greater role in the future. A modern system should not only know that a field exists; it should also understand why that field exists. For example:
A field named "Days_Due_with_Discount" already contains significantly more information than a cryptic name like "Field_4711".
If the meaning of this field, how it is used, and its context are also documented, this creates a knowledge base that both humans and AI systems can understand.
This is precisely why gFM-Business has been consistently documented over many years. Thousands of fields, processes, and relationships have been described. What was originally intended for developers and users is now increasingly evolving into a semantic knowledge layer for AI systems.
Documentation as a Competitive Advantage
For a long time, documentation was considered a necessary evil in many software projects. It was often neglected or created only at the end of a project. Many companies have systems whose original developers are no longer available. Knowledge of important relationships has been partially lost.
AI is changing this perspective as well. Documentation suddenly becomes a strategic advantage. AI can only deliver good results if it understands the underlying structures. Well-documented systems therefore have an enormous advantage over solutions whose knowledge is stored exclusively in the minds of individual developers.
This insight has also had a major impact on the development of SchallOS. The platform is not just meant to manage code; it is meant to manage knowledge.
Why Decades of Expertise Are Suddenly Worth Their Weight in Gold
When people talk about modern software development, the discussion often centers on new programming languages, frameworks, or cloud technologies. However, another question is at least as important:
What knowledge has been accumulated over the past few decades?
After more than thirty years of FileMaker development, we have gained a wealth of insights. These include not only technical experience, but above all insights into business processes, user behavior, and the practical requirements of day-to-day business operations.
This also highlighted where traditional development platforms reach their limits. In FileMaker, numerous workarounds had to be developed over many years. Fields were stacked on top of one another because certain display formats could not be achieved any other way. Scripts had to handle complex tasks that should actually have been built into the platform. Many solutions worked exceptionally well, but they were often piecemeal and time-consuming to maintain.
These experiences served as an important starting point for the development of SchallOS. The central idea was not to copy or replace FileMaker. The central idea was to translate a similar development philosophy into a more modern architecture.
- An architecture that consists less of thousands of individual objects and relies more on reusable functional containers.
- Architecture that incorporates AI from the very beginning.
- And an architecture that focuses more on business logic and domain expertise than on technical details.
The true strength of artificial intelligence, therefore, does not lie in generating more code. Its true strength lies in translating knowledge accumulated over decades into working software more quickly and efficiently. In my view, this is precisely where the biggest change for developers lies.
The idea behind the SchallOS Business Operating System
SchallOS wasn't conceived on the drawing board. The platform is the result of more than three decades of practical development experience and is based on software that has been in productive use for nearly 14 years.
When gFM-Business was founded many years ago, the initial goal was relatively modest. The aim was to create a flexible Enterprise software that can be adapted to different industries and meets the typical needs of small and medium-sized businesses. Over time, however, it evolved into much more than just a traditional ERP solution. CRM, invoicing, Article management, Warehouse, Projects, Inventory, Human Resources, Document Management, E-Invoices, Interfaces, and numerous other features were added.
With every client project, we gained new knowledge. With every enhancement, the software became more comprehensive. At the same time, we built up a very extensive knowledge base regarding real-world business processes and the day-to-day needs of companies.
One decision in particular was especially important—even though it initially had nothing to do with artificial intelligence. A few years ago, we began systematically documenting gFM-Business. Fields, tables, processes, and relationships were described and recorded in a structured manner. At the time, this was done primarily for open licenses, developers, and users. Today, it is clear that this very documentation has become a crucial foundation for the next stage of development.
After all, suddenly it’s not just developers who can use this information. Modern AI systems are also capable of accessing this knowledge and understanding the connections.
Why SchallOS Is Not a FileMaker Clone
Anyone looking at the first screenshots of SchallOS will quickly recognize the project's roots. That's not surprising, either. After all, much of the experience and many of the ideas stem from more than thirty years of working with FileMaker.
Still, we never planned to simply replicate FileMaker. A mere replica would have made little sense. The world has changed. Modern browser technologies, powerful databases, local AI systems, and new development tools open up possibilities that simply didn't exist ten or twenty years ago.
The real question, then, was: What would a development platform look like if we could start from scratch today while drawing on three decades of practical experience?
SchallOS was born precisely from this question. The platform incorporates many of the core principles that have made FileMaker successful. These include rapid development of business applications, a strong visual component, and the ability to implement complex solutions without large development teams.
At the same time, many aspects have been deliberately reimagined. Functional containers are increasingly replacing thousands of individual layout objects. Semantic descriptions and AI-powered development are replacing complex chains of scripts. Many technical workarounds are being replaced by platform features designed from the ground up for modern web applications.
The goal is not to replace FileMaker. The goal is to create the next stage in its evolution.
Preserving Knowledge Instead of Starting Over
One idea remained central throughout the development process. Over the past years and decades, many developers have accumulated an enormous amount of knowledge. They know their customers, their processes, their data structures, and their solutions down to the last detail. This knowledge is often far more valuable than the actual program code.
Nevertheless, many companies regularly find themselves caught in the same cycle. New technologies appear on the market. Old systems are replaced. Existing solutions are discarded, and the whole process starts all over again.
That is exactly the approach I wanted to avoid. SchallOS was born out of the conviction that existing knowledge must not be lost. The investments made in recent years should not become worthless simply because the underlying technology is changing.
That is why migrating existing solutions plays a central role. It is not just data that should be transferred; structures, processes, business logic, and application knowledge should also be preserved to the greatest extent possible.
For this reason, the upcoming version, gFM-Business 9, will be particularly significant. It not only represents the next stage in the evolution of the existing FileMaker solution, but also serves as a bridge to the next generation of platforms.
Key New Features in gFM-NEXT / SchallOS
| Function | Description | Benefits |
|---|---|---|
| Functional Container | Navigation elements, dialog boxes, and complete modules as intelligent components. | Fewer objects, better maintainability, and AI support. |
| Semantic Language Layer | Objects know their technical meaning. | Automatic translations and intelligent AI features. |
| Label on the field | The label is an integral part of the field object. | Up to 50 fewer % layout objects. |
| Conditional Data Types | Objects can change their type dynamically. | Fewer workarounds and more flexibility. |
| SQL in Object Properties | Dynamic content directly in labels and properties. | Reduces the number of auxiliary fields and scripts. |
| Smart Paste | Smart import of existing objects. | Faster migration and development. |
| Container Registry | Centralized management of all components. | Versioning and Reuse. |
| AI-powered development | Automatic code generation from business logic. | Significantly faster development speed. |
Migrating Existing Solutions
Migration is a challenging issue in many projects. Often, migration involves exporting data and then importing it into a completely new system. The actual application then frequently has to be rebuilt from scratch. Forms, workflows, and user interfaces are recreated. A great deal of knowledge is lost in the process.
For SchallOS, therefore, a different approach was chosen. The platform is designed to understand existing solutions as comprehensively as possible. Table structures, fields, relationships, layouts, and business processes form the foundation for this. Step by step, a migration layer is being developed that can analyze existing applications and convert them into modern components.
Of course, the first version won't be able to automatically recognize every feature just yet. That would be unrealistic. Nevertheless, the foundation for a significantly smarter form of migration is already being laid today.
In the long term, the goal is to create a system that not only imports existing solutions but also understands their structure. In my view, this is precisely one of the biggest differences compared to many traditional new developments.
SchallOS doesn’t start from scratch. The platform is built on a well-established ERP solution, decades of practical experience, and an extensive knowledge base. This makes it possible to preserve what has been proven effective while taking advantage of modern technologies. The past is not being replaced. Rather, it forms the foundation for the next generation of business applications.
Highlights from gFM-NEXT and SchallOS
Functional containers instead of a jumble of objects
Anyone who has developed business applications over many years is familiar with this problem. With every new feature, the number of objects on a layout grows. Additional fields are inserted, more buttons are added, new scripts are written, and more and more special cases are taken into account. Eventually, you end up with an application that works perfectly well, but whose internal structure is becoming increasingly complex.
Consequently, creative solutions often had to be found, especially in traditional development environments. Fields were overlaid to enable different display formats. Buttons were hidden and only displayed under certain conditions. Additional helper objects took on tasks that should actually have been part of the platform. These techniques work and have proven themselves over many years. Nevertheless, they increase the complexity of an application in the long run.
During the development of SchallOS, the same question therefore kept coming up:
If you could start from scratch today, how would you design a modern layout mode?
A layout mode for developers
One of the most important requirements was to maintain the precision of traditional rapid development systems. While many modern web frameworks offer enormous technical capabilities, they often fail to match the efficiency of a well-designed visual layout editor. That is why SchallOS’s layout mode is deliberately modeled after the strengths of established development environments.
Grid, Guide lines, magnetic alignment, multiple selection, object grouping, and precise positioning are, of course, standard features of the system. The goal was never to develop a simplified web editor. Rather, the goal was to combine the speed and precision of traditional development tools with a modern architecture.
At the same time, numerous concepts were reimagined to eliminate the need for the typical workarounds of the past.
Fewer objects, more intelligence
Field labels are a good example of this. In many systems, an input field consists of at least two objects. The actual field and its corresponding label must be managed, positioned, and translated separately.
In SchallOS, field labels can be an integral part of a field object. This provides developers with complete flexibility. Internally, however, the number of objects required is significantly reduced.
At first glance, this approach may seem unremarkable. However, in larger applications with thousands of fields, it makes a huge difference. Fewer objects mean less administrative overhead, clearer layouts, and easier maintenance.
At the same time, this approach opens up new possibilities. Since labels are directly linked to the field, they can be automatically translated via the semantic language layer. The developer no longer has to maintain separate translations for each instance. The system understands the meaning of a field and can automatically provide the appropriate language variants.
Dynamic content instead of technical workarounds
Another goal was to make as many areas of the platform as possible dynamically usable. In many applications, additional workarounds are created because certain properties do not support calculations. Developers must therefore use auxiliary fields, triggers, or additional scripts to display dynamic content.
SchallOS takes a different approach here. Dynamic content should be possible wherever text can be entered. This includes, for example, field labels, placeholder text, text objects, help text, and control properties.
In addition, calculations, SQL queries, or other dynamic expressions can be used. This allows many tasks to be solved right where they are needed. The need for technical workarounds is significantly reduced.
Of course, classic features such as conditional formatting, conditional visibility, and dynamic activation of objects remain an integral part of the platform. These mechanisms have proven their worth over many years and continue to be among the most important tools in the development of modern business applications.
Familiar Objects, Modern Architecture
Despite all the new features, the platform is designed to feel familiar to experienced developers. That’s why SchallOS continues to include most of the object types found in traditional development environments. Fields, buttons, tabs, controls, lists, containers, charts, and other object types are still available.
The key difference, however, lies beneath the surface. While many systems treat each object largely in isolation, SchallOS operates on a significantly more semantic level. Objects understand their role within an application. They are no longer merely graphical elements, but part of a larger architecture.
This makes it possible to identify patterns, automate translations, and integrate AI systems much more deeply into the development process.
The Real Innovation: Functional Containers
The most visible manifestation of this philosophy is the function container. A function container can perform a small task. For example, it can display a chart or provide a search function.
Similarly, however, a function container can also contain an entire administrative area. Multiple tab pages, complex dialogs, custom data access, security logic, and extensive user interfaces can all be combined within a single container.
In layout mode, a function container is still just an object. This shifts the complexity from the user interface to clearly defined, reusable components.
A navigation bar becomes a function container. A toolbar becomes a function container. An administration interface becomes a function container. Even complete business modules can be implemented as standalone containers. This approach significantly reduces the number of visible objects while creating a much clearer architecture.
From FileMaker Scripts to AI-Powered Components
This concept becomes particularly interesting when combined with artificial intelligence. The original FileMaker scripts often serve as a source of knowledge in this context. They describe business logic, workflows, and processes that have evolved over many years.
However, the actual program code of a function container is not simply carried over. Instead, the AI analyzes the existing logic, understands the business requirement, and generates a modern implementation within the new architecture. This preserves the knowledge while allowing the technical implementation to be built from scratch.
This is precisely where one of the platform's greatest advantages lies. It is not the old code that is preserved, but the knowledge behind it.
Migration Without a Fresh Start Using the Clipboard
This principle also applies when migrating existing solutions. If the MBS plugin is installed on the FileMaker side, tables, fields, layout objects, scripts, and other elements can be imported directly via the clipboard. The platform analyzes the content and uses it to create the corresponding structures within SchallOS.
In addition, Smart Paste provides a feature that goes far beyond traditional pasting. Before importing, you can select which components should actually be included. At the same time, you can make adjustments before the data is even pasted.
A typical example would be converting a quote form into an order form. Instead of manually adjusting all the fields afterward, the necessary transformations can be performed during the import process itself. This results in a significantly more intelligent migration process than with traditional import tools.
The Foundation for the Next Generation of Business Applications
Function containers are therefore much more than just a new object type. They form the foundation of an architecture that is consistently geared toward reusability, semantic knowledge, and AI-driven development.
Combined with the modern layout mode, the integrated language layer, the advanced object features, and the intelligent migration tools, the result is a platform that is both familiar and fundamentally new.
The goal is not to copy existing systems. The goal is to preserve the strengths of traditional rapid development environments while fully leveraging the capabilities of modern AI technologies.
Migration from FileMaker to SchallOS / gFM-NEXT
| Component | Migration | Distinctive Feature |
|---|---|---|
| Tables | Automatically | Import of structure and metadata. |
| Fields | Automatically | Descriptions become part of the semantic layer. |
| Layouts | Smart Paste | Objects can be customized during import. |
| Scripts/CF | AI Analysis | Business logic is transferred to function containers. |
| Value lists | Automatically | Direct migration to the new platform. |
| Modules | Semi-automatic | Automatic container recognition is planned for the long term. |
| Translations | Semantic Language Layer | Multilingualism can be largely automated. |
The Technical Architecture
When discussing new software platforms, many conversations initially focus on visible features.
- What modules are available?
- What kinds of reports can be generated?
- Which interfaces are supported?
These questions are important. In the long run, however, it is usually something else that determines a platform's success.
Architecture forms the actual foundation. It determines how flexibly a system can be expanded, how stable it is under load, how well new technologies can be integrated, and how easily applications can be further developed in the future.
For this reason, the development of SchallOS did not begin with a focus on individual features. Instead, the central question was how a modern platform should be structured so that it can still be meaningfully expanded in five or ten years.
The result is a multi-tier architecture that integrates traditional business applications, modern web technologies, and artificial intelligence.
The AI Layer as a New Level of Development
One unique feature of SchallOS is that artificial intelligence is not treated as an additional module. Rather, AI forms its own layer within the platform.
In many systems today, AI is integrated as an afterthought. A chat window is added, an assistant is built in, or an interface to an external service is created. The actual architecture remains unchanged.
SchallOS takes a different approach. From the very beginning, the platform was developed with the understanding that AI would play a central role in development, documentation, and maintenance in the future. That is why the AI accesses not only data but also documentation, architectural descriptions, container definitions, and semantic information.
This results in a system that not only manages data but also possesses knowledge about its own structure. For developers, this makes a significant difference. The AI not only recognizes individual code fragments but also understands the interrelationships within the platform.
Runtime Mounts and Container Registry
Another important component is the Runtime-Mounts and the Container Registry. Today, modern applications often consist of many independent components. Navigation bars, toolbars, dialogs, business modules, and administration areas are no longer considered rigid parts of a layout but are managed as standalone units.
The Container Registry handles the central management of these components. Each function container has a unique identity, its own properties, and a defined lifecycle. The runtime, in turn, ensures that the relevant components are loaded and executed at the right time.
This approach offers several advantages. First, it creates a clear separation between layout and functionality. Second, components can be further developed, replaced, or expanded independently of one another.
In addition, the registry lays the groundwork for future features such as version control, signing, security levels, and central component libraries.
IndexedDB as a local truth layer
SchallOS deliberately uses modern browser technologies for local storage. IndexedDB plays a central role in this. It is a powerful database technology that is available directly in the browser and can efficiently manage even large amounts of data. Unlike traditional browser storage solutions, IndexedDB was specifically designed for complex applications.
This offers several advantages for SchallOS. Layouts, configurations, metadata, and other information can be stored locally. As a result, applications remain usable even without a permanent network connection. At the same time, response times are fast because much of the data is available directly on the local system.
This is an important factor, especially for development tools and large-scale business applications.
"Committed-First" Instead of "Cache Chaos"
During development, it quickly became clear that modern applications require not only fast storage but also a clear layer of truth.
Many systems use various caches, buffers, and temporary states. While this can increase speed, it often leads to errors that are difficult to trace in the long run.
That is why SchallOS relies on what is known as a "committed-first" architecture. New information is not considered valid until it has been successfully stored and verified. Only then does it become visible to other components.
This approach ensures significantly greater consistency within the system. At the same time, it simplifies troubleshooting and reduces the risk of inconsistent states. This concept has proven to be extremely helpful, particularly when dealing with complex layout operations and managing a large number of components.
PostgreSQL for Network and Multi-User Operations
Of course, local storage alone is not sufficient for professional business applications. That is why PostgreSQL serves as the foundation for network operations, teamwork, and server-based installations.
For many years, PostgreSQL has been one of the most powerful and reliable open-source database systems available. The database is used worldwide in enterprise applications, cloud platforms, and large web services. The combination of IndexedDB and PostgreSQL results in a flexible architecture.
Single-user solutions can be run locally. Multi-user environments use PostgreSQL as a central database. At the same time, hybrid scenarios remain possible, in which local data storage and central server structures are combined.
This creates a platform capable of supporting both small single-user applications and comprehensive enterprise solutions.
An Architecture for the Coming Years
Ultimately, the technical architecture of SchallOS has a simple goal: complexity should not disappear; it should be moved to the right place.
Users should be able to focus on their work. Developers should be able to focus on business logic and domain expertise. The technical infrastructure is responsible for reliably connecting data, components, and processes.
The AI layer, container registry, runtime mounts, IndexedDB, PostgreSQL, and the committed-first architecture are not simply a collection of individual technologies. They are part of an overarching concept.
This concept is intended to lay the foundation for a new generation of business applications—applications that leverage modern web technologies while retaining the speed, flexibility, and productivity of traditional rapid development systems.
Runtimes, Deployment, and the Return to Simplicity
Anyone who developed business applications twenty or thirty years ago often recalls a time when software distribution was surprisingly straightforward. An application was created, tested, and then delivered to the customer. In many cases, a single installation was all it took, and the software was immediately ready for use.
Of course, the systems back then were technically much simpler than today's solutions. Nevertheless, they had one key advantage: their complexity was manageable for both developers and users.
The situation has changed significantly in recent years. Modern applications often consist of numerous components. Web servers, databases, certificates, cloud services, security policies, container technologies, and hosting platforms must all be integrated with one another. For large companies, this is a given. For many smaller companies and independent developers, however, this development poses a significant hurdle.
Yet many users really want just one thing: an application that works reliably and is easy to deploy. This is exactly where SchallOS's deployment strategy comes in.
Single-user operation without unnecessary hurdles
Not every application requires a server, cloud infrastructure, or complex network architecture. Many solutions are used by individual users or small teams. In such scenarios, the technical infrastructure should require as little attention as possible.
The combination of modern web technologies and local data storage makes it possible to run applications even without a constant server connection. Layouts, settings, metadata, and other information can be stored locally. This ensures that applications remain fast, flexible, and independent of a constant Internet connection.
This approach is deliberately designed to evoke the simplicity of classic development environments. It leverages modern technologies without burdening the user with unnecessary complexity.
Network Operations for Teams and Businesses
As soon as multiple users start working together, the requirements change. Data must be stored centrally. User permissions must be managed. Changes must be available to everyone involved.
That is why the SchallOS architecture has supported traditional multi-user operation from the very beginning. With PostgreSQL serving as the central database, applications can be run on a network without the need to maintain different versions of a solution. Data is available centrally, while the user interfaces remain flexible.
This offers a significant advantage for businesses. The same application can be used both locally as a single-user solution and in a larger multi-user environment. This is intended to make switching between different operating models significantly easier than with many traditional systems.
Browser mode as the default
Today, the development of modern business applications takes place primarily in the browser. There are good reasons for this. Browsers are available across platforms, do not require complex installations, and allow for quick updates.
For this reason, SchallOS is based entirely on modern web technologies. The browser is not viewed as a limitation, but rather as a runtime environment. Today, powerful data management, local storage, modern user interfaces, and complex business logic can all be executed directly within the browser.
This creates a platform that can be used on Windows, macOS, Linux, and many other systems without having to develop a separate application for each platform.
At the same time, the option remains to transition applications to other operating modes at a later date.
SaaS and Centralized Deployment
In addition to on-premises installations and network environments, Software as a Service naturally plays an important role as well. Many companies today prefer centralized solutions delivered over the Internet. Updates are distributed automatically, users access the same application from different locations, and the technical infrastructure is managed centrally.
The SchallOS architecture therefore takes SaaS scenarios into account from the very beginning. Thanks to the clear separation of the user interface, runtime, and data storage, applications can be operated both locally and centrally. Developers do not have to rebuild their solutions from scratch for each deployment model. Instead, a common technical foundation is created that supports different deployment models.
Flexible Deployment Strategies Instead of Technical Dead Ends
A common problem with modern software platforms is that early architectural decisions make it difficult to add new features later on.
Once you choose a particular operating model, you often have to stick with it for the long term. Switching from an on-premises installation to the cloud—or from a cloud solution to an on-premises environment—can be time-consuming and costly.
SchallOS deliberately takes a different approach here. The platform is designed to give developers as many options as possible. Standalone operation, network operation, browser applications, and SaaS solutions are not viewed as competing concepts. They are different use cases of the same architecture.
This allows developers to choose the operating mode that is best suited to their clients and projects.
The Return of Simplicity
Perhaps this is precisely the most important idea behind the SchallOS deployment concept. The world of technology is not going to get any simpler in the coming years. New technologies, new security requirements, and new integrations will continue to emerge.
At the same time, modern software development should not be unnecessarily complicated. Many developers still remember a time when applications could be created quickly, distributed easily, and maintained without difficulty. This simplicity was one of the reasons why rapid development systems were so successful for decades.
SchallOS does not attempt to replicate the past. The technical requirements of modern applications are simply too different for that. Rather, the goal is to combine the simplicity of earlier development environments with the capabilities of modern web technologies. Developers should be able to focus on their applications, not on the complexity of the infrastructure.
If this succeeds, it will create a platform that is not only powerful but also fun to use again. Ultimately, that is precisely the idea behind runtimes, flexible deployment, and the deliberate return to a simpler approach to software development.
Deployment Options with SchallOS
| Deployment Type | Technical Basis | Typical Application |
|---|---|---|
| Single-user | Browser + IndexedDB | Self-employed individuals and small businesses. |
| Network Operations | Browser + PostgreSQL | Working groups and teams. |
| Corporate Server | PostgreSQL Server | Multi-user operation in a business setting. |
| SaaS | Cloud Infrastructure | Multi-client online solutions. |
| Hybrid operation | IndexedDB + PostgreSQL | Offline work with synchronization. |
| Runtime | Packaged Application | Easy distribution to end customers. |
The Roadmap: gFM-Business 9 as a Bridge to the Next Generation
The coming months mark an important milestone in the development of gFM-Business and SchallOS. The release of gFM-Business 9 for FileMaker and gFM-NEXT on the SchallOS platform is scheduled for September 2026. This is not simply another update to an existing ERP solution. Rather, this version plays a special role within our future strategy.
gFM-Business 9 will be the last major release based on the classic FileMaker platform. This does not mean that the solution will disappear. On the contrary. Existing customers can continue to use the software productively, existing installations will remain in place, and new installations will still be possible.
At the same time, however, gFM-Business 9 will lay the technical foundation for the transition to the next-generation platform. The focus here is on the new migration wizard, which is designed to make it significantly easier to transfer existing customized open-license solutions to the new architecture. Table structures, fields, layouts, scripts, and other components can be analyzed and prepared for migration. This creates, for the first time, a direct connection between the existing FileMaker ecosystem and the new SchallOS platform.
SchallOS as a Development Platform
About two months after the release of gFM-Business 9, the first public version of the SchallOS Business platform is scheduled to be released. The focus is not on end users, but on developers.
In its first phase of development, SchallOS will primarily serve as a development platform for FileMaker developers. It is aimed at developers and companies that want to modernize or expand their existing solutions, or transition them to a new technological foundation over the long term.
The focus here is not on completely rebuilding existing applications. What is far more important is the ability to preserve existing investments and gradually migrate them to the new architecture. The first versions will therefore focus particularly on the following areas:
- Migration of Existing Solutions
- Layout Development
- Functional Container
- semantic knowledge layers
- AI-powered development
- Modern Deployment Models
It is already clear today that this approach offers significant potential. Many tasks that previously had to be carried out manually in a time-consuming manner can now be performed much more efficiently through a combination of documented expertise and AI support.
Long-term outlook
The release of SchallOS does not mark the end of development, but rather the beginning of a new phase. Many of the concepts being discussed today will continue to evolve in the coming years. These include, among others, intelligent migration technologies, automatic container recognition, semantic development tools, and AI-powered architectural features.
A long-term goal is not only to import existing applications from a technical standpoint, but also to understand their structure and meaning. The more knowledge that is available within the platform, the better future AI systems will be able to support development, maintenance, and expansion.
The first version of SchallOS lays the foundation for this. The real journey begins after that.
The Server Manager for gFM-NEXT and SchallOS
Early-Bird Period Extended Through July 31
The development of upcoming versions has generated a great deal of interest in recent months. Numerous customers, developers, and interested parties have been following the development of gFM-Business and SchallOS for some time now and would like to actively participate in the next steps.
For this reason, the originally planned early-bird phase is being extended. Interested parties will still have the opportunity to take advantage of a 20 percent discount through July 31. This promotion applies not only to new customers but also specifically to existing customers who are planning to upgrade their current solution.
Investment Security for Existing Solutions
One important point concerns existing gFM-Business users. The release of gFM-Business 9 does not mean that this version of FileMaker will no longer be usable. The solution will remain available and can continue to be used in a production environment.
At the same time, future functional development will increasingly shift toward SchallOS. This provides existing customers with a clear path forward. Investments in gFM-Business will remain in place and can be gradually migrated to the new platform generation at a later date.
It is precisely this idea that underpins the entire strategy behind SchallOS. Rather than starting from scratch or discarding existing knowledge, the goal is to integrate existing experience, processes, and solutions into a modern architecture, thereby laying the foundation for the next generation of business applications.
Carrying Proven Knowledge into the Future
The story of SchallOS doesn't begin with artificial intelligence. Nor does it begin with modern web technologies, PostgreSQL, or function containers. It begins with a simple question:
How can we transfer the knowledge we've built up over decades to a new generation of technology without having to start from scratch?
This is precisely the question that many developers and companies are grappling with. Over the past few decades, countless applications have been developed, processes optimized, and experience gained. Often, this involves thousands of hours of work and a vast amount of expertise. At the same time, technologies are changing at an ever-faster pace. New platforms are emerging, old systems are disappearing, and many companies face the challenge of protecting their investments while still remaining future-proof.
This is where SchallOS comes in. The goal is not to replace existing solutions with something entirely new. Rather, the aim is to build a bridge between proven systems and modern technologies. An application developed today in FileMaker should not necessarily lose its appearance, usability, or business logic simply because it is migrating to a new technical platform.
Ideally, the application will look virtually identical to the user after migration. Workflows remain unchanged. Users will still be able to navigate the system easily. At the same time, the solution runs internally on a modern architecture that offers new possibilities for expansion, automation, and scaling.
This approach becomes particularly exciting because of the semantic layer. As soon as an application consists of more than just fields, tables, and scripts—and instead understands its own meaning—entirely new possibilities emerge. Translations can be automated. Documentation can be automatically generated or updated. AI systems can understand business processes instead of merely analyzing program code. This creates a fundamental difference from many previous development approaches. While traditional systems primarily manage data, a semantic platform is increasingly capable of managing knowledge. In my view, this is precisely where one of the greatest opportunities of the coming years lies.
20 % Discount through July 31.
Valid for New purchases, Upgrades and future
gFM-NEXT and SchallOS projects.
The discussion about artificial intelligence often focuses on text, images, or chatbots. For developers, however, the real revolution lies elsewhere. For the first time, AI makes it possible to incorporate expertise built up over decades directly into modern software architectures. This does not replace the developer’s experience. It enhances it.
SchallOS therefore does not see itself as an alternative to existing development platforms. Rather, the platform was created out of the conviction that proven concepts remain valuable. Rapid development, visual design, flexible data models, and productive tools will remain important in the future. At the same time, modern web technologies, semantic knowledge layers, and AI-supported development open up possibilities that would have been unthinkable just a few years ago.
The upcoming versions of gFM-Business 9 and SchallOS therefore do not mark the end of an existing product line, but rather the beginning of a new phase of development—a phase in which existing investments can be preserved while new technologies become available.
After more than thirty years of software development, I am now more convinced than ever that knowledge is a company's most valuable resource. Databases, programming languages, and technical platforms will continue to evolve.
Knowledge of customers, processes, products, and business operations, however, remains the true core of every successful application.
Frequently asked questions
- What exactly is SchallOS?
SchallOS is a new development platform for business applications, born out of more than 30 years of practical experience with FileMaker and the development of gFM-Business. The goal is to combine proven concepts from classic rapid development systems with modern web technologies, artificial intelligence, and a semantic knowledge layer. The focus is not on reinventing all processes, but rather on migrating existing solutions to a modern architecture. - Is SchallOS intended to completely replace FileMaker?
No. SchallOS was not created out of a desire to replace FileMaker. Rather, the platform is intended to provide a way to transition existing knowledge and solutions into a new technological generation. FileMaker remains a powerful development environment that allows for very fast and effective software development. SchallOS is designed to open up additional possibilities, particularly in the areas of AI, modern web architecture, and flexible deployment models. - Why was SchallOS developed in the first place?
This development arose from the observation that many companies and developers have built up valuable solutions over the course of decades. At the same time, technologies are changing at an ever-faster pace. SchallOS is designed to prevent this knowledge from being lost simply because the technical foundation has changed. The goal is to protect existing investments while also making modern technologies usable. - What sets SchallOS apart from traditional low-code platforms?
The most important difference lies in the combination of semantic knowledge, AI support, and portability. While many platforms primarily provide tools for developing new applications, SchallOS also aims to understand and adopt existing solutions. The semantic knowledge layer plays a central role in this process. - What are function containers?
Function containers are intelligent components that can handle part or even all of a module’s functionality. A navigation bar, a toolbar, a search field, or even a complete administration interface can be implemented as function containers. This significantly reduces the number of individual objects while increasing reusability and maintainability. - Why are functional containers so important?
Function containers shift complexity away from the layout and into clearly defined components. Instead of having to manage hundreds of individual objects and scripts, you end up with self-contained functional modules, each with a clear purpose. This makes applications more organized, easier to maintain, and significantly better suited for the use of artificial intelligence. - Can an existing FileMaker solution be migrated to SchallOS?
That is precisely why the migration layer is currently being developed. The goal is to migrate tables, fields, layouts, scripts, and other components of existing FileMaker solutions to the greatest extent possible. In the long term, the platform should not only be able to import data, but also understand the structure and meaning of an application. - Will my application's appearance remain the same after migration?
This is one of the most important development goals. A migrated application should remain as familiar as possible to users. Layouts, user interfaces, and workflows can be retained to a large extent—and in most cases, even entirely—while the technical foundation is modernized. This makes the transition significantly easier for companies. - What role does artificial intelligence play in SchallOS?
AI is not just an add-on module, but a central component of the architecture. It supports development, documentation, analysis, migration, and, later on, the expansion of existing solutions. The platform was designed from the outset so that AI systems can understand the underlying structures. - What does "semantic knowledge layer" mean?
A semantic knowledge layer describes not only technical structures but also their meaning. The platform not only knows that a field exists but also understands what that field is used for. This is what makes intelligent features such as automatic documentation, translations, and AI-powered development possible in the first place. - Can applications be automatically translated into other languages?
The semantic architecture of SchallOS lays the foundation for this. Because the platform understands the meaning of fields, labels, and objects, translations can be automated to a much greater extent than in traditional systems. This significantly reduces maintenance efforts and facilitates international projects. - Which database does SchallOS use?
IndexedDB is used for local applications. PostgreSQL is used for multi-user environments and server solutions. This allows both single-user applications and larger enterprise solutions to run on the same platform. - Why does SchallOS rely on PostgreSQL?
PostgreSQL is one of the most powerful and reliable database systems in the world. The database is flexible, scalable, and ideally suited for professional business applications. At the same time, it offers an open and future-proof technological approach. - What does "Committed-First Architecture" mean?
With this approach, changes are considered valid only after they have been successfully saved and verified. This creates a single source of truth within the platform. As a result, errors caused by outdated caches or inconsistent states can be significantly reduced. - What are the benefits of the new layout mode?
Layout mode combines the precision of traditional development environments with modern capabilities. Grids, guides, magnetic alignment, and many other features are available. At the same time, numerous concepts have been reimagined to eliminate the need for typical workarounds found in older systems. - When will gFM-Business 9 be released for the FileMaker platform?
The release of gFM-Business 9 is scheduled for September 2026. This version includes numerous improvements as well as the new migration wizard, which is intended to lay the groundwork for a future transition to SchallOS. - When will SchallOS be available?
According to current plans, the first public version of SchallOS is scheduled to be released about two months after gFM-Business 9. The initial focus will be on developers and companies that want to migrate existing solutions to the new platform. - Who is SchallOS particularly suitable for?
The platform is primarily aimed at FileMaker developers, existing gFM Business customers, and companies with business applications that have evolved over the long term. SchallOS is particularly appealing to anyone who wants to protect their existing investments while also benefiting from modern technologies and artificial intelligence.
Markus Schall has been developing individual databases, interfaces and business applications based on Claris FileMaker since 1994. He is a Claris partner, FMM Award winner 2011 and developer of the ERP software gFM-Business. He is also a book author and founder of the M. Schall Publishers.
