Frequently asked questions

Everything we see on applications are derivatives of data structures contained in the backend database. A centralized data model is the key to unlocking "low code" benefits for the enterprise, which increases development velocity by over 50%. Moreover, a centralized data model provides better team coordination, and offers true agility with relational data - allowing model iteration as part of the natural development process.

We provide graphical tools where either you can design your data model, or we can extract the data model from an existing database. Once we have the data model, we can often deploy an initial demo at no-cost. This can be handy for submitting a prototype as part of an RFP.

Splicer is designed with support for existing databases at its root. We primarily use xsd technology to extract a meta model from an existing RDBMS.
 

Splicer also supports NoSQL databases. This means you can deploy a common data model to both RDBMS and NoSQL.

We are designed for companies that use a Spring Boot (java) server stack.  We support both Angular and React for webpages.  For mobile, we support both PWA and native mobile apps.

Splicer is complementary to AI.  Since our paid subscribers recieve the application source code, they can use whatever AI engine to help with customization.  

Nevertheless, we plan to leverage our patents for AI features as outlined in this Medium post.

Github continous integration workflows run after every commit.  These build source code, run all integration tests, and run vulnerability checks against the NVD upon every push to the github repo.