Generated by All in One SEO v4.9.8, this is an llms.txt file, used by LLMs to index the site.

# Hapsah

Write apps in your own words

## Sitemaps

- [XML Sitemap](https://www.hapsah.org/sitemap.xml): Contains all public & indexable URLs for this website.

## Posts

- [Blogs](https://www.hapsah.org/?page_id=55)

## Pages

- [Write smart apps in your own words](https://www.hapsah.org/) - Write apps in your own words. Create intelligent automation solutions using natural language to define the rules and knowledge graph.
- [Lecture: Ontology and Business rules in practice](https://www.hapsah.org/lecture-ontology-and-business-rules-in-practice/) - Lecture:Ontology and Business rules in practice Tuesday 7 October 2025 Bas van der Raadt gave a lecture for the course 'Knowledge Organization' at Vrije Universiteit Amsterdam (VU Amsterdam).Where he talked about:- Problems with code based systems- Why ontology driven AI systems are needed- What is an ontology?- How to verbalize an ontology- What is a
- [Blogs](https://www.hapsah.org/blogs/) - Blogs about the Hapsah platform and approach
- [Where are my business rules?!](https://www.hapsah.org/where-are-my-business-rules/) - Where are my business rules?! There is a lot of talk about data being the most valuable asset of your business. But there is something even more important: Business rules. They determine how you treat your customers. But how do you treat your business rules? Give them some love! Data is not the most valuable
- [Solutions](https://www.hapsah.org/solutions/) - Select a prefab solution as a kickstart and make it your own With Hapsah you don't have to start from scratch. You can select a predefined app and then fully customize it to your needs. We have solutions for any industry. Agriculture, Forestry and Fishing Arts, Entertainment and Recreation Accommodation and Food Service Activities Electricity,
- [Try now](https://www.hapsah.org/try-now/) - Write app In Hapsah modeler you can write your app in natural language code.Don't be shy and give it a try. Start writing Run app While writing, you're always one click away from running your app. Don't be shy and let your app fly. Click & run Too shy? Check out our tutorials Go to
- [Tutorial: Hello world!](https://www.hapsah.org/hello-world/) - Quick start: Hello world! Our goal with Hapsah.org is to allow anyone who can read and write to create apps by writing (controlled) human language text. This sounds like the holy grail for software engineering. So what does this look like? In this blog I will show you using a (sort of) hello world example:
- [Tutorials](https://www.hapsah.org/tutorials/) - Tutorials Learn writing apps with Hapsah using these tutorials. From the basics of creating nouns and verbs, to the more advanced topics like writing statements and rules. All tutorials follow one example app of a grocery store. You can navigate directly to a specific tutorial via links below or click the 'get started' button below.
- [Terms](https://www.hapsah.org/terms/) - Terms of service Last revised: November 3, 2023 Effective date: November 3, 2023 Welcome to Hapsah – the site that lets you write apps in your own words. Hapsah is both a visual programming tool and a cloud platform. You use the programming tool to build your applications, while they are hosted and run on
- [What are reference data?](https://www.hapsah.org/what-are-reference-data/) - What are reference data? Reference data are data that structure or control other data. Often reference data are stored in what people call ‘Code tables’. A very well known example is the ISO 3166-1 country code table. This way you don’t have to manage a list of countries yourselves. And it makes data exchange easier.
- [Connection between Ontology and Business Rule](https://www.hapsah.org/connection-between-ontology-and-business-rule/) - How are an ontology and a business rule connected? Ontologies and Business Rules are different things, but they are connected. So much connected that Business Rules can't even exist without an Ontology! In this blog, we will show how they are connected following a simple example. Before we start If you do not yet know
- [Ontology and Business Rules in an Event-Driven Architecture](https://www.hapsah.org/event-driven-architecture-2/) - Ontology and Business Rules in an Event-Driven Architecture Event-Driven (Business) Architecture (EDA) helps in building efficient value chains where high quality data is produced and exchanged. Adding Ontology and Business Rules perspectives to an Event-Driven Architecture helps increasing its efficiency and effectiveness even further. In this article we show how this works. We start with
- [Tutorial: Create new instance](https://www.hapsah.org/tutorial-create-new-instance/) - Tutorial: Create new instance Before any rule can fire, you need to enter data into your app. The first step of entering data is to create instances of the things that you defined: Entity instance: An instance of an entity type. Descriptor instance: An instance of a descriptor type. The most common situation is that
- [Tutorial: Rule actions](https://www.hapsah.org/tutorial-rule-actions/) - Tutorial: Rule actions As soon as a rule contains one condition, you can add actions to that rule. Actions define what happens when a rule is fired. There are two kinds of rules: Find: determines which other entities or values, that are not yet available in the rule, will be searched for when the rule
- [Tutorial: Rule elements](https://www.hapsah.org/tutorial-rule-elements/) - Tutorial: Rule elements The first step in writing a rule is selecting which elements play a role in the when part, being the conditions that trigger the execution. The two types of elements that can be added to the conditions of a rule are: Entity instance: an instance of an entity type as defined in
- [Tutorial: Rule conditions](https://www.hapsah.org/tutorial-rule-conditions/) - Tutorial: Rule conditions After having added elements to a rule, the next step is to define conditions. Conditions determine when a rule is triggered for execution. Conditions come in three forms: Association: when an Entity instance is associated with another Entity instance. Attribution: when an Entity instance has a certain type of Attribute or Descriptor
- [Tutorial: Statements](https://www.hapsah.org/tutorial-statements/) - Tutorial: Statements When you're finished defining the nouns and verbs for your app, as a next step you can write statements that connect these nouns via verbs. A statement is a sentence that is considered to be generally true in your app, and is therefore written in plural. In Hapsah, a Statement always has the
- [Difference between Ontology and Business Rule](https://www.hapsah.org/ontology-versus-business-rule/) - What is the difference between an Ontology and a Business Rule? This is a question we often get. In this article we will explain both concepts, and show you how they are interrelated. In short, an Ontology defines the structure and meaning of the type of things (entities) within a domain, whereas Business Rules define
- [I entered my data. What happens next?](https://www.hapsah.org/i-entered-my-data-what-happens-next/) - I entered my data. What happens next? So you just entered a bunch of data in a web form. When you click 'submit' you receive a message: “Thank you for your request. We will try to process it within 10 workdays”. Seriously?! Can't this be done differently? Dealing with the black box The other day
- [About](https://www.hapsah.org/about/) - Our journey Why is writing apps made so difficult? Why can’t I read the technical code? How do I know for sure how my app works? And how can I show to my users that my app does no harm to them? These questions have kept us awake for a long time. That is why
- [Tutorial: Check rule results](https://www.hapsah.org/tutorial-check-rule-results/) - Tutorial: Check rule results The final step in using an Hapsah app is to check the outcomes of rules that may have fired due to entering data (creating instances) and relating data (associating entities). As explained earlier, the conditions of a rule determine when a rule fires. The actions of a rule determine which data
- [Tutorial: Associate entity instances](https://www.hapsah.org/tutorial-associate-entity-instances/) - Tutorial: Associate entity instances When you've entered at least two entity instances that may be associated with each other, you can choose to associate them. Like entering data while creating new instances may trigger rules with equation conditions to fire, associating entity instances with each other may trigger rules with association conditions to fire. So,
- [Use clear language](https://www.hapsah.org/use-clear-language/) - Use clear language Yesterday, I saw a poster of a cinema festival in my town called "Go short". At first I thought it was about stock trading. But the guiding picture showed a cinema visual. So I was confused! Confusion kills innovation Confusion about terminology happens all the time within organizations. And the extensive use
- [You can build something unique with no-code & low-code!](https://www.hapsah.org/build-something-unique/) - You can build something unique with no-code & low-code! Most no-code and low-code app development platforms get you up-and-running with a new app in no-time. But when you want to build something unique and long-lasting, they are not always the best choice. Why not with no-code? Most no-code platforms allow you to quickly combine prefab
- [Seeing is believing](https://www.hapsah.org/seeing-is-believing/) - Most people find an abstract idea hard to follow. But they can relate to a concrete example. Showing a live demo to customers is crucial in getting a positive vibe going in transformations and innovations. But this is harder in practice than you'd think. How can you decrease the time to build a meaningful demo?
- [Our vision](https://www.hapsah.org/our-vision/) - Tech as it should be We all heavily depend on technology. The apps we use and the data we share. But tech is too complex for most people. We feel this is not fair. That is why we made the first no-code platform that speaks your language. Write what you want When you can explain
- [Tech benefits](https://www.hapsah.org/tech-benefits/) - A few tech things we're proud of We spent much time on providing not only an easy-to-use platform, but also ensuring that our platform is technically sustainable. flexible All changes are processed 'on the fly'. No manual changes to screens, code, data or API are needed, ever. Version control is also automatically managed for you.
- [Tutorial: Rule operations](https://www.hapsah.org/tutorial-rule-operations/) - Tutorial: Rule operations When you've added added elements and conditions to your rule, then you can add operations to manipulate values where needed. Operations can also be used in the actions of a rule. There are two types of operations: Unary: operations that take one operand as input. Binary: operations that take two operands as
- [Tutorial: Rules](https://www.hapsah.org/tutorial-rules/) - Tutorial: Rules After having defined your nouns, verbs and statements, you can define the active elements of your app by writing rules. A rule consists of three parts: When: the conditions under which the rule will execute. Then: the actions that will be performed when the rule executes. Do: the operations that are used in
- [Tutorial: Verbs](https://www.hapsah.org/tutorial-verbs/) - Tutorial: Verbs After having defined the nouns for your app, the second step is to create verbs. Verbs define the connections between the nouns of your app. There are two types of verbs you can create: Associations: the relationships between entities (e.g. Customers use Shopping carts). Attributions: the assignments of characteristics (attributes and descriptors) to
- [Tutorial: Nouns](https://www.hapsah.org/tutorial-nouns/) - Tutorial: Nouns The first step in writing Hapsah apps is creating nouns. Nouns make out the atomic elements of your app. There are three types of nouns you can create: Entities: the things of interest in your app (e.g. Customer). Attributes: the characteristics of the things in your app (e.g. First name). Descriptors: groupings of
- [Roadmap](https://www.hapsah.org/roadmap/) - Product roadmap We are pushing hard to get Hapsah from its current state of a prototyping tool to a ready for real life smart app development platform. We still need to work on the following feature categories. Usability Improve the user experience for both modeler and running app environments. User management, privacy and security Integrate
- [Tutorial: Run app](https://www.hapsah.org/tutorial-run-app/) - Tutorial: Run app Up till now, we have discussed only things about writing apps. Now it is time to test your app by running it! While writing your app, everything is about defining types (nouns, verbs and statements) and defining rules. Running your app is all about creating and changing instances of those types. So,
- [Citizen app development](https://www.hapsah.org/citizen-dev/) - True citizen app development Easy to understand If you can read and write, you can use Hapsah. Apps are written in natural language code. You don’t need any technical knowledge, ever. no limits There are no limitations to what you can build and adjust. This counts for both the data and business rules of applications.
- [Learn more](https://www.hapsah.org/learn-more/) - Enjoy human readability and tech soundness combined together Hapsah offers a true citizen app development experience through its natural language modeling environment. It also provides a lightweight and easy-to-maintain platform with clear tech benefits. I want to learn more about: Citizen app development Tech benefits

## Ideas

- [Question driven data entry](https://www.hapsah.org/idea/question-driven-data-entry/) - Allow for question driven data entry alongside the classic form driven data entry.
- [Add strategic business goals and objectives as guiding framework](https://www.hapsah.org/idea/add-strategic-business-goals-and-objectives-as-guiding-framework/) - To capture the rationale behind business rules and why they are designed that way
- [Query builder](https://www.hapsah.org/idea/1025/) - Add query builder to Hapsah modeler. Make query language based on natural language questions instead of classical 'select' instructions like SQL.
- [Threshold definition](https://www.hapsah.org/idea/threshold-definition/) - Define global thresholds that can be used across all rules (e.g. large deal size => $500,-)
- [Definitional rules](https://www.hapsah.org/idea/definitional-rules/) - Add rules that define new concepts out of existing ones (e.g. A gold customer is a Customer that commits to 10 large deals per year). Allow these new concepts to be used across multiple rules.
- [Constraint rules](https://www.hapsah.org/idea/constraint-rules/) - Add rules that define the things that may not happen instead of what must happen (Action rules)
- [Analysis of rule effectiveness](https://www.hapsah.org/idea/analysis-of-rule-effectiveness/) - Allow for continuous analysis of rule execution outcomes to optimize effectiveness.
- [User management](https://www.hapsah.org/idea/user-management/) - Integrated user management including authorization structure of allowed data manipulations by users and consent management for rule execution triggered by those data manipulations.
- [Webhooks for push notifications](https://www.hapsah.org/idea/webhooks-for-push-notifications/) - Make more visible to users that rules have executed by sending push notifications to front-end web app.
- [Decentralized identity integration](https://www.hapsah.org/idea/decentralized-identity-integration/) - Integrate with solidproject.org for authentication (based on decentralized identify) and personal data access control.
- [Decentralized file storage integration](https://www.hapsah.org/idea/decentralized-file-storage-integration/) - Integrate with IPFS and Filecoin for decentralized storage.
- [Integrate with decentralized knowledge graph](https://www.hapsah.org/idea/integrate-with-decentralized-knowledge-graph/) - Integrate with the Underlay for decentralized knowledge graph capabilities.
- [Make Hapsah itself decentralized](https://www.hapsah.org/idea/make-hapsah-itself-decentralized/) - Change the architecture from monolith to decentralized / distributed.
- [Visualization of rules](https://www.hapsah.org/idea/visualization-of-rules/) - Use GraphView to visualize the structure of a rule, showing the interrelations between its conditions, operations and actions.
- [Interactive app dashboard](https://www.hapsah.org/idea/interactive-app-dashboard/) - Nicer, more interactive overview of app contents instead of static table of buttons as it is now.
- [REST API documentation](https://www.hapsah.org/idea/rest-api-documentation/) - Automatic generation of swagger documentation.
- [REST API generation](https://www.hapsah.org/idea/rest-api-generation/) - Dynamic API generation based on changes made in nouns, verbs and statements in Hapsah modeler.

## Boards

- [Feature log](https://www.hapsah.org/ip-board/roadmap/)

## Status

- [Open](https://www.hapsah.org/ip-status/open/)