Free yourself from
manufacturer dependency!

FieldBots OS and Connect

FieldBots integrates service robots for facility management through Cloud-to-Cloud connections or native IoT integrations to enable real-time communication between your swarm and the FieldBots Cloud.

Read documentation
Internet best practices and long-termย partners

FieldBots uses a technological basis that is considered state-of-the-art today and, apart from the business logic, is largely supplier- and stack-independent. Based on the user and their use cases, processes were modeled that were created thanks to proven concepts, products, and providers.

  • The microservice infrastructure FeldBots Connect was originally forked from the middleware product FieldPass of a sister company of the same name FieldPass GmbH. Customers of FieldPass use its product for the operations of reliable, scalable, and secure clouds for tens of thousands of robots and employees.
  • The sister company Feil, Feil & Feil GmbH, and its counterpart in the Philippines, FFUF Manila Inc., are the perfect partners in case FieldBots and its customers need additional development resources or plan individual integration projects.
  • For the secure administration of identities, roles, and rights, FieldBots Connect uses Keycloak, which has become an industry-wide standard and offers an audited implementation of OpenID Connect and OAuth 2.0.
  • FieldBots relies on Microsoft Azure, which has made a name for itself in the business world over the last years. All environments of FieldBots are hosted and professionally operated on the European data centers of Microsoft.
  • The European Tuya cloud is used as our IoT hub for stable and secure integrations of FieldBots natively-supported service robots.
  • Angular
  • Kotlin
  • Flutter
class BotService { constructor(private botRepository: BotRepository) { } loadAllBots(): Observable { return this.botRepository.getAll({ type: Type.CF170, page: 1, maxResults: 100, }); } }
class Bots( private val botApi: BotApi ) { suspend fun loadAllBots(): List { return botApi.getAll( type = Type.CF170, page = 1, maxResults = 100, ) } }
class BotService { final BotRepository botRepository; Future> loadAllBots() { return botRepository.getAll( type: TypeCF170, page: 1, maxResults: 100, ); } }
Basic approach
in development

10 years of experience in the digitisation of building operations and their service providers have created paradigms in the corporate group, which FieldBots also follows. They guarantee a solid, future-proof overall product without making the mistakes that often occur when starting to develop a new product.

  • โญ•๏ธ API first approach
  • โ™€๏ธ Focus on users and use cases
  • ๐ŸŒ Internationalisation
  • ๐Ÿš€ Multi-platform technologies
  • ๐Ÿ Offline capabilities
Development Practices
Standardised Processes

FieldBots OS and Connect have been developed using a proven, agile process based on state-of-the-art technology and the industry’s best practices. We use the infrastructure as code tool Terraform to set up environments and deployment pipelines. Binding branch management according to Gitflow allows for the controlled rollout of individual features based on epics and user stories. Systematic code reviewing by our software architects with a precise process for pull requests is part of our development standard, as is proper test coverage through unit tests. Linting automatically prevents widespread abnormal behavior in the development phase.

Operational Concept
Professional Operations

FieldBots OS and FieldBots Connect benefit from a professional, GDPR-compliant operation of microservices in Microsoft Azure Cloud’s European part. Regular updates ensure that FieldBots remains secure and sustainable. FieldBots’ live environment, including its apps and underlying microservices, is monitored systematically and automatically. Second-level support for your technical queries is available during business hours (Monday to Friday, 8:00 a.m. to 6:00 p.m.).