Zero Trust Data API

Move data across the cloud with zero trust security and reliable access control. How? Galeva makes structured data vanish when it's not used. Nothing here to steal.

Ontological Data

In Galeva, structured data does not exist at rest. It comes into existence only during an authenticated query. This means that even a successful attempt to bypass authentication is useless. Not only does this protect against accidental data exposure and backdoor data breaches, it immensely lowers the risk profile of thecontrollers and processorsthat handle large quantities of sensitive data. See ontological data.

Effective GDPR Compliance

With ontological data, data at rest is unstructured and unreadable. This means that Galeva has complete control over who accesses what. Restrict data operations to specific roles. Restrict entities to roles. Finally, add users to those roles. Galeva's unique authentication that brings structured data into existence makes data authorization that much more powerful.

Automated Administration

Galeva automatically optimizes your queries and automates indexing. How can Galeva possibly do this without knowing app usage patterns? It's all in the structure. Galeva's unique relational structure is consistent and has algorithmically predictable data growth. She easily and consistently handles any query and indexes efficiently. See API docs.

What is ontological data?


ontological
adjective | of or relating to ontology, the branch of metaphysics that studies the nature of existence or being

ontological data
noun | data whose existence is conditional upon the existence of data operations such as a query

Features

Easy Data Configuration

Galeva has an easy to use web app that makes data configuration a breeze. Configure entities and relationships, upload data, manage users and roles, and so much more. Backend maintenance is easy.

Access Control

Users can be assigned roles. Access to entities can be restricted for specific roles. Access controls such as these in the data level help application developers develop robust and secure applications.

Intuitive REST APIs

Galeva provisions all CRUD (create, retrieve, update, delete) operations and transactions in the database through intuitive REST APIs. Application development is fluid, organized, and highly productive.

Ready for Change

Changing business requirements and application requirements usually mean re-building. Not here. An ontological architecture easily accommodates structural changes and Galeva's APIs simply work without any recompilation or re-indexing.

API Examples

    {
      "attributes":
      {
        "CUSTOMER":
        [
          "FIRSTNAME",
          "LASTNAME"
        ],
        "ADDRESS":["*"]
      },
      "filters":
      {
        "CUSOMTER":
        {
          "FIRSTNAME":
          {
            "condition":"=",
            "value":"Mike"
          },
          "LASTNAME":
          {
            "condition":"=",
            "value":"Johnson"
          }
        },
        "ADDRESS":{}
      },
      "join":["CUSTOMER","left","ADDRESS"],
      "rowcount":500
    }
              
POST slice

POST slice handles complex queries involving multiple entities, joins, and filters. Slice through your data exactly the way you want.

This request retrieves 100 or less customers named Mike Johnson and their addresses.

        bactchsize: 1000
        dataid: 20200211110451
        startsfrom: 3000
              
GET set

POST set handles large queries for batch processing. After execution, GET set processes the results in multiple batches. Perfect for analytics.

This request retrieves 1000 rows after the 3000th row.

    {
      "1":
      {
        "operation":"insert",
        "entity": "expense",
        "data":
        { 
          "name":"lunch",
          "amount":"210"
        },
      },
      "2":
      {   
        "operation":"update",
        "entity": "account",
        "data":
        {
          "balance":
          {
            "oldValue":"4000",
            "newValue":"3790"
          }
        },
      }
    }
              
POST transaction

POST transaction initiates a transaction involving multiple operations that must all either succeed together or fail together.

This request performs an insert and an update which will be committed in the database together