Wow! this looks promising I want to use it for a Backoffice app is a valid use case?

Is it secure? Any limitations on the data I can import?

Hi Mimisole the platform is multitenant with each app isolated in its workpsace, with profile and permissions sets you can specify user permissions up to the field level.

We haven't implemented the batch data import functionality yet but the only limitation we will have is the batch size. You can insert data one at a time for now.

We are currently in beta. you can try to create a small example Backoffice app on the platform to try out what we offer and if it suits you.

if you need any help setting up your workspace or have any questions we are on discord.

The platform is really something worth having a look at! It saves you lots of time writing tedious repetitive crud code or another data querying engine. Also it provided much needed security access control out of the box for different user roles. Must try!

Thanks f1ght4fun. I agree with both points here - most backend developers find it boring and time consuming creating new or modifying existing crud APIs every time the business requirements change.

Now as far as the data query engine, I can feel the pain of whoever tries to choose the best ORM out there. For the last few years there were a lot of efforts to abstract away anything related to databases (native sql, admin, internals etc) but all of them have serious limitations at the end of the day.

With Appteum we try to handle all of these pain points for you, so developers can focus on the business requirements they have in front of them.

Happy to hear what you plan to use Appteum for. Hop in our Discord and we can chat: https://discord.gg/8ETmPedepG

Disclaimer: Appteum co-founder.

i don't see any other use case for this tool other than simple crud apps. what if my app needs to expose data over web sockets or i need to implement an operation that is not an api request? how does this compare to supabase?

You are right andneo the platform as it stands now is suitable for building CRUD applications since what we currently offer is to setup you objects fields, user permissions and data APIs through configuration.

We plan to implement data streams and workflows with Lambda style functions that will cover even the most complex application demands in the near future.

Supabase is a nice service with a lot of functionality but requires that you know advanced features of postgres (rls policies etc ..) to properly setup your data security.

With supabase you are bound to what features can be developed on top of postgres which is a double edge sword in my opinion. in addition, we believe that our simple sql syntax over API is much more intuitive and easy to learn in contrast to postgrest syntax.

Saw your product and joined the beta version that you released and have some questions from technical aspects of the software.

1) We are a team that building software programs for our clients, what is the benefit technical wise and business wise to use your platform instead create everything from scratch by us?

2) The object that we're creating in your system, how you're handling and storing the data?

Thanks serkis85 glad to hear that you joined our beta. - Technical wise we provide the backend scaffolding, so as a developer you don't need to handle the infrastructure, db, APIs etc. for your app. Once you configure your backend settings we use this configuration as metadata and handle everything it needs to be done in the background. Using our APIs/SDK in your code is like you have your db, apis, and security in a single library.

Business wise, using Appteum saves you all that time you would otherwise need to set up and maintain your backend if you choose to create everything from scratch.

- If I understood your question correctly you are referring to the security of your data. Appteum is a multitenant platform with each workspace being physically isolated, we designed the system this way to provide maximum security for our users. In addition to the internal security of your data, we provide profiles and permission sets where you can configure the access your user has to your data up to the object/field level.

Gns89 thanks for your proper response. Now I see the benefits and the logic behind. Looking forward to using the appteum more and build an app base on it. thanks

I used the beta version of the platform and it seems very promising for CRUD APIs.

I have some questions:

1) Can I export my data?

2) Can I archive my data?

3) Do you have rate limit?

4) If I have an entity with huge amount of data, can I use slicing instead of pagination?

Thanks geomatblue. - At the moment you can export all your data using our APIs. Would adding an export functionality to csv format be valuable to you? - We dont have any archive feature at the moment but we could easily add soft-deletes is it the same for your use case? - For the duration of the beta we dont have any rate limits on accounts other than the maximum records you can fetch in a single batch using our GET API. We plan though to add API rate limits later on. - You can combine both slicing and cursor based pagination. I will give you an example: You can use the GET API [0] and limit the amount of data to retrieve using the LIMIT keyword and subsequently call the CURSOR API [1] and control the batch size using the x-query-batch-size header

Hope it helps, let us know if you have any other questions/comments.

[0] https://docs.appteum.com/api/#tag/Objects/operation/ObjectsS... [1] https://docs.appteum.com/api/#tag/Objects/operation/ObjectsS...