r/software • • 3d ago

Looking for software Need a good database software that has features like airtable

Hello!

My primary experience is with Airtable and my new company will not purchase it going forward as it is to expensive (84K for 2 years). I need to see what alternatives there are with the constraints I have. Biggest constraint is that the software package has to be self contained and I cannot use outside plugins. I have immediate access to Sharepoint (with powerapps), Access, Excel, and PostgreSQL but I dont think any of them fit my needs, but would love more input from people a lot more knowledgeable in these software's. So this is my use case: I am wanting to build a relational database. Each 'sheet' has parent information that I can connect together in a form. Sheet A, has entires like cat, dog, Sheet B has Colors like blue, red, and I can have sheet C that can have inputs from a form that users can connect the data. I can add pictures and other info. I can then have a dashboard that can create graphs from the data or search bars that I can search for 'Dog" and it shows me all entires related to "Dog'. I also need this software to be able to handle formulas and tie in the different sheets. I can Pull in Dog+Blue=BlueBerry and output into Sheet D. So the biggest things are: Able to connect the data, have data input through forms, able to create dashboards that can show the data through graphs, have KanBan style dashboards where I can show Status of certain fields. Airtable was the perfect software for my needs, so I need a Airtable equivalent but I just dont have any experience with other softwares to dig into them.

0 Upvotes

16 comments sorted by

3

u/PeterPook 3d ago

Why were you hired?

2

u/carnage123 3d ago

To setup production chains, not build databases

1

u/FinancialSurvey5794 3d ago

Haha exactly. Sounds severely unqualified.

0

u/carnage123 3d ago

hmm, maybe I wasnt hired to build databases but instead have another actual job and this is soley to help me organize my job better? You guys are fucking worthless

1

u/FinancialSurvey5794 3d ago

start the timer before you're "let go". I hope you didn't actually tell them to spend 84K on a software because you couldn't do your job.

3

u/vermyx 3d ago

You want to build a relational database....but can't use a relational database like Postgres? And apparently ms forms, Excel, and Power Automate all fit the bill but you can't use that either? Your new company wont spend the money because you already have those tools

0

u/carnage123 3d ago

I can use those tools, I dont have experience with them, that is what Im saying. So I dont know if those softwares will behave in the way that I need them to. Im saying that is what I have available, but seeing if anyone with experience with those softwares is able to comment if those softwares can do what I want it to do. From my research, Postgres can build a relational database, but does have the ability to build out a UI without going to a third party. With Sharepoint, It looks like I can do some functions, but from what I gather its actually not a relational database so the data might get messy. Im asking if people have first hand expereince, can I do what I did in Airtable in the softwares I have avaiable.

1

u/gaseous_rapidity 3d ago

check out baserow or nocodb, both are open source and work kinda like airtable without the crazy price tag

1

u/Wilbis 3d ago

Nocodb out of those should at least work. I don't have experience with Baserow.

2

u/Redjeepkev 3d ago

Easily don't in excel. I don't see the issue?

2

u/BranchLatter4294 3d ago

You can do this easily in Access.

1

u/carnage123 3d ago

I dont think you can build out the same type of data views as you can in airtable

1

u/VortecaDEV 3d ago

I’d actually start with Microsoft Access, considering the tools you already have available.

It supports relational tables, forms, queries and calculated fields, so quite a few of your Airtable requirements should be achievable without additional software.

The biggest limitation will probably be the interface, especially if you want something like Kanban boards.

If several employees need browser access, Power Apps with SharePoint Lists could be worth exploring instead.

PostgreSQL is great as a database, but you’d still need to build an interface around it.

I’d suggest building a small prototype in Access first before committing to anything.
Out of curiosity, how many people would need to use the system simultaneously?

1

u/carnage123 2d ago

I appreciate the actual help. About 50 people would be in and out of it. But with Access, multiple people cannot be in it at the same time right? Im looking deeper into what access can and cannot do. Its been hard googling and researching these softwares because sometimes its like, yea they all can do what I need, but then sometimes it tells me, no, its not what you need. So wanting to put in a ton of effort into something for it not to work out would suck.

1

u/VortecaDEV 2d ago

Access actually does support multiple users at the same time.

I just have looked this up and Microsoft officially lists a maximum of 255 concurrent users, although that's a technical limit rather than a guarantee of good performance in practice.

For your situation, you'd typically use a split database. The backend stores the data on a shared network location, while each colleague runs their own local copy of the Access frontend.

With around 50 colleagues using the system occasionally, this could work, depending on how many are actively using it simultaneously and how complex the operations are.

The important thing is how you and your colleagues would actually use the system day to day.

If you're mainly viewing or updating records from computers on the same office network, Access could be a reasonable starting point.

However, if colleagues need access from different locations, want to work through a browser, or frequently update the same data, I'd lean towards a web-based solution instead.

My biggest advice would be to build a small working prototype first. Test it with realistic data, multiple users and the actual workflows you need before investing weeks into developing the entire system.

And I completely understand your concern. The last thing you want is to spend a significant amount of time building something, only to discover it doesn't properly support what you and your colleagues need.

A small proof of concept could save you a lot of time and frustration down the road.