Less repetitive work
No need to build logging, event handling or access management from scratch. Use string, list, date and time, and other utility functions from a shared library.

Start your project with ready-to-use, tested components. RIXCAT Ignite® provides user and access management, logging, module collaboration, integrations and utility functions, so your team can spend more time on your solution’s business logic.
No need to build logging, event handling or access management from scratch. Use string, list, date and time, and other utility functions from a shared library.
The framework’s components grew out of needs that recur across projects. Their testing and refinement are grounded in 15 years of practical use.
Develop your own modules and connect them to the rest of your system using RIXCAT Ignite® mechanisms. Partners can build and sell their own solutions on the framework.
RIXCAT Ignite® supports the fat database approach: business logic runs in Oracle Database and uses the framework’s functions. Oracle APEX provides the user interface.
Administration · monitoring · your interface
Your business logic + RIXCAT Ignite® components
Synchronous and asynchronous calls; background jobs
HTTP(S) · email · SFTP · S3
Tables, PL/SQL packages, views and other objects. Your solution’s business logic accesses framework functions through database interfaces.
A separate service connects the database with external services. It is delivered as a container for Docker or Podman.
Ready-to-use applications for system administration and monitoring. Developers also receive a starter application with an authentication plug-in.
Authentication with a password or the unified sign-in module (VPM). A security profile defines access conditions, including whether a client digital certificate is required.
Access rights are organised into three levels: privileges, roles and responsibilities. Module availability can be defined at organisation and user level.
A client certificate is an additional access condition. Microsoft Active Directory integration is retained as a legacy option; its use in a particular project must be discussed separately.
To separate organisations’ data, tables include an organisation identifier column, such as ORG_CORGID. Session management provides a function that returns the current session’s organisation identifier.
Developers must include the organisation filter in the solution’s SQL queries. Alternatively, Oracle Virtual Private Database (VPD) may be used where licensing permits. The identifier column and session context do not automatically enforce data isolation on their own.
Modules are deployed in separate database schemas. The API manager publishes an interface from one module for use by others, generating the required grants, views and synonyms.
Modules can also collaborate through event publishing and subscription (publish/subscribe). This interaction takes place within the database — the API manager is not a REST layer.
Ready-to-use support for HTTP(S), SMTP, Microsoft Exchange, FTP(S), SFTP, Amazon S3 and MinIO, as well as SMS delivery.
Calls can be synchronous with an execution timeout or asynchronous. Background jobs can also be initiated. External services are connected and configured to suit the project.
Shared mechanisms for logging system events and errors, monitoring operations and handling support requests. Available from the start of your project.
The APEX administration and monitoring applications complement the database components with a working environment for managing the system.
Shared functions for strings, lists, date and time processing, and other common development tasks. The product also includes a virtual file system.
APEX applications can use RIXCAT Ignite® functions, for example to validate input fields. The starter application with its authentication plug-in helps you begin interface development.
Medical functionality belongs to RIXCAT NOVA modules. DataNode and the warehouse module are not included in RIXCAT Ignite®. Oracle security capabilities, such as data encryption and database auditing, are used according to the selected environment and licence. Centralised certificate management is not part of RIXCAT Ignite®.
External AI tools can help build APEX interfaces and parts of the business logic on top of RIXCAT Ignite® components. Ready-made AI generation tools are not included in the product.
A separate perpetual licence is required for each production instance/PDB. It includes the related development, test and standby environments. Licensing and maintenance are separate: when maintenance ends, you may continue using the version received, but new fixes and support are no longer available.
Partners are encouraged to develop and sell their own modules and complete solutions. The production environment requires an RIXCAT Ignite® licence. The end customer may purchase maintenance even where the solution developer originally purchased the licence.
RIXCAT® does not support customer-modified RIXCAT Ignite® components. Modified RIXCAT Ignite® code may not be resold.
The customer or their maintenance provider installs fixes in the customer’s environment. Installation by RIXCAT® and adaptation of the customer’s solution are agreed separately or use the hours included in the maintenance package. In most cases, a short service interruption is needed — typically 10–15 minutes.
RIXCAT® works to maintain backward compatibility. Customers are responsible for testing their solution after patches are installed.
Each production instance/PDB has its own 12-month maintenance package, also covering the related development, test and standby environments.
Email answers, access to fixes and 8 working hours per year.
Bronze features, change request assessment and a total of 38 working hours per year for consultations and minor changes.
Gold features and a total of 108 working hours per year for team support and solution development.
Fixing RIXCAT Ignite® defects during active maintenance does not consume the included hours. Investigating and resolving issues in customer code, configuration or infrastructure does consume working hours. Unused hours do not carry over; additional work is agreed in advance. Pricing and terms are set out in the proposal.
The framework is used in both RIXCAT® solutions and partner projects. The business functionality of the systems below is provided by their project-specific modules.
A survey and structured data collection platform developed by Sunberry Systems on RIXCAT Ignite®. Supports monitoring and patient experience assessment, with integration into existing information systems.
Explore aptauja.comA solution for vaccination reporting, vaccine logistics, stock tracking and electronic orders. Healthcare provider functions are available through Latvia’s e-health portal.
Latvian e-health portalA customer relationship management solution for a financial services provider, using RIXCAT Ignite® as its technical foundation.
A system for outpatient healthcare providers. Reception, consultations, billing and other medical modules extend the RIXCAT Ignite® foundation.
Explore RIXCAT NOVAManagement of family support programmes, educational activities, regional events and surveys. Sunberry Systems has built its own modules on RIXCAT Ignite®, including business participant and contract management for the Latvian Honorary Family programme.
Vieta ģimeneiA system for recording and analysing energy efficiency and mandatory electricity procurement component (OIK) reports. RIXCAT® has a supporting role in the project. The system has active users; new features are not currently being developed.
ENER systemARKA — a structured survey solution developed with Sunberry Systems; RIXCAT® has a supporting role.
PASIS — a medical service classification project developed by RIXCAT®.
External links lead to project websites or access portals. Using system functions may require authentication and appropriate permissions.
Tell us about your development team, existing Oracle environment and planned solution. We will explore how RIXCAT Ignite® components could help your project.