Keeping the homes of tomorrow safe.

Orban is a powerful automation system designed to enhance user experience through customization and innovation. However, with great flexibility comes great responsibility. To ensure the system remains safe, stable, and secure, we’ve established these development guidelines. Failing to follow them may result in revocation of publishing rights, legal action, or other penalties.

1. STABILITY

Just as you wouldn’t build a house on a weak foundation, Orban must be built on solid, stable code. Maintaining the integrity of Orban is crucial, especially when adding new features or third-party modules. Here's how to ensure stability:

• Test Thoroughly: Before introducing any new code, benchmark and stress-test your module or feature. Observe its behavior over time to ensure it functions correctly, even under high load or unusual conditions.

• Third-Party Additions: When using or integrating third-party code, understand that we cannot guarantee its stability. Be cautious and vet any external modules before installing them.

• Community Reviews: We plan to implement a community-driven review system where users can rate modules based on their stability, performance, and overall experience. This will help identify and promote reliable, well-maintained modules.

Failure to provide stable and reliable code may result in your module being flagged or removed from the Orban

ecosystem. Repeat offenses could lead to a permanent ban on publishing verified modules.

​

​

2. SAFETY

Safety is our top priority. Orban must never be used in ways that could harm people, interfere with medical devices, or compromise personal security. The following rules are non-negotiable:

• No Medical Equipment Control: Orban MUST NOT be used to control, interfere with, or override medical equipment or life-sustaining devices. This includes but is not limited to:

  • CPAP Machines

  • Ventilators

  • Pacemakers

  • Nebulizers

  • Insulin Pumps

  • Infusion Pumps

  • Dialysis Machines

  • AEDs or Defibrillators

  • Emergency Alert Equipment

These devices are designed to sustain or preserve human life and must remain under uninterrupted, manual control. Any attempt to automate or tamper with these systems through Orban will be seen as gross negligence, and you WILL BE HELD ACCOUNTABLE for any harm or loss of life caused. Violation of this guideline could lead to criminal charges and legal prosecution.

​

​

3. SECURITY

Security is essential when dealing with home automation systems. Orban allows for integration with a wide range of devices, but we have strict guidelines for handling potentially dangerous systems like door locks and personal data:

• Door Lock Automation: Orban supports automated door locks, typically using ESP-32 boards or similar hardware. While these locks can be configured and controlled via Orban, malicious behavior is strictly prohibited. Any module that manipulates door locks must adhere to the following guidelines:

  • No Backdoors: Modules must not contain hidden functionalities that compromise security.

  • Full Transparency: All features and capabilities must be clearly stated before installation. Any failure to disclose actions or features, such as hidden unlocking mechanisms, countdown attacks, or autonomous unlocking, will result in serious penalties.

  • Notifications: The user must always be notified of any lock/unlock actions, failed attempts, or errors.

If a custom lock system is created, it must comply with these security measures. Any intentional exploitation or breach of the system will result in immediate prosecution.

​

​

4. PRIVACY

Orban is committed to protecting user privacy. Data mining, collection, or unauthorized access to user data is strictly forbidden. Developers must respect user privacy at all times, which includes the following:

• No Data Collection AT ALL: You may not collect, store, or transmit user data (e.g., voice commands, configuration settings, personal files). If your module requires data collection, you must:

  • Not do that. Keep it to yourself.

    ​

•  

​

​

5. TRANSPARENCY

All modules submitted to Orban must be transparent in their functionality. This means developers are responsible for providing clear and detailed documentation for their modules, including:

• Purpose: Clearly state the intended purpose of the module.

• Interaction: Explain how it interacts with Orban, connected devices, and other modules.

• Permissions: List any permissions the module requires and why they are necessary.

• Limitations: Document known bugs, security vulnerabilities, or potential issues.

Failure to provide adequate documentation will prevent your module from being approved for the Orban ecosystem.

​

​

6. ACCOUNTABILITY

As a developer for Orban, you are accountable for the behavior and functionality of your modules. If your module causes harm, violates these guidelines, or breaches security protocols, you may face penalties, including:

• Revocation of publishing privileges.

• Legal action for negligence or harm caused.

• Permanent removal from the Orban developer community.

The health, safety, and privacy of our users are of the utmost importance. These guidelines are designed to protect the integrity of Orban and ensure that it remains a trusted, stable, and secure platform.

By contributing to Orban, you agree to these guidelines and commit to upholding the highest standards of stability, safety, and security.

​

​

7. RESTRICTED DEVICES AND BEHAVIOR

There are some boundaries on the types of devices and behaviors that can be integrated or automated through Orban, particularly when they pose risks to physical safety or ethical standards. The following practices are strictly forbidden:

• Harmful Devices: Orban must never be used to control or operate devices that can inflict harm or cause injury to others. This includes, but is not limited to:

  • Weapons: Any device capable of causing bodily harm, such as firearms, knives, or other dangerous tools.

  • Hazardous Machinery: Any automated device with the potential to harm humans or animals (e.g., heavy machinery, mechanical traps).

• Booby-Trapping: Automating traps, harmful mechanisms, or dangerous setups in your home, workplace, or other areas through Orban is prohibited. Any attempt to use Orban to create environments that cause injury to others, either intentionally or accidentally, will be subject to immediate legal action.

• Sexualized Machines: Orban is not to be used for the creation or automation of sexual devices or self-pleasuring machines, especially those that involve bodily insertion or interaction. Creating or distributing modules for these purposes violates the ethical standards of the platform and will result in immediate removal and legal consequences. Also, that's really gross. Please don't ever do that.

​

We Appreciate Your Cooperation, But Please Create Responsibly.

-Rowan Cross, director of Orbitan Technologies.