Peliqan Reviews & Product Details

We look after several legal companies, and each one has its own Exact Online administration. Every connection gives you the same tables, but they're separate, so any report across all companies meant repeating the same work per company.

Peliqan has a data app template called union connection data. You run it, pick the connection type, select the connections and the tables you want to combine, and click Generate queries. It creates the union queries in their own folder and activates them as views. Each row gets a source column that tells you where it came from, and the columns and data types are lined up across all of them.

We built our dashboards on those views. When we add a company, we run the template again instead of rewriting SQL. Review collected by and hosted on G2.com.

It took us a moment to find, because it's a data app template rather than a menu option. Once we knew that, it was a few clicks. Review collected by and hosted on G2.com.

A large part of our data sits in a SQL Server on our own network, and it has to stay there. That ruled out most cloud tools for us. Peliqan gave us more than one way to connect it. We could whitelist their IPs on our firewall, set up a VPN, or install their Windows agent, Satellite, on a server inside the network. We went with Satellite, and it syncs the SQL Server data into Peliqan. After that the tables worked like any other source. We join them with our HubSpot data in SQL, and the reporting runs from there instead of from manual exports. Review collected by and hosted on G2.com.

We spent some time internally choosing between the agent and the VPN, because both would have worked for us. It's worth deciding that with your IT team before you start. Review collected by and hosted on G2.com.

We wanted a small internal app on top of our business data, built with Claude Code, without setting up our own database, login and hosting for it. In Peliqan we created a new machine in the Peliqan Machine section, connected our coding agent through the Peliqan CLI, and downloaded the instructions.md file for Claude Code to work from. Claude Code built the app and deployed it over SSH with the CLI. We checked the preview, then clicked Publish to production. Review collected by and hosted on G2.com.

You need to be comfortable in a terminal for the CLI part. For the person on our team who already codes, that was fine. Review collected by and hosted on G2.com.

We inherited a system with a few hundred tables, no documentation and nobody left who had built it. Working out how anything joined to anything else was going to be weeks of guesswork. Peliqan has a template app that detects foreign key relations for you, so we ran that first and got a usable picture of the relational model without reverse engineering it by hand. From there we worked through the Grid view adding descriptions to the tables and columns that mattered, so the next person would not have to repeat the exercise. Review collected by and hosted on G2.com.

The relation detection gets you most of the way rather than all of it, so we still had to check its work and add a few it had missed. Given the alternative was doing all of it by hand, we were not complaining. Review collected by and hosted on G2.com.

A client's application needed a clean feed of data that lived across three of their systems. Rather than build a service to sit in front of all that, we prepared the dataset with SQL and published it as an API endpoint straight from Peliqan. Their developers consumed it directly.

That took the whole middle layer out of the project. No server for us to run, no auth to write ourselves, and when they asked for two extra fields we changed the query and it was live Review collected by and hosted on G2.com.

Nothing on the endpoint itself. We spent longer than we expected deciding how to shape the query behind it, but that was our own design call rather than anything to do with the platform. Review collected by and hosted on G2.com.

This is the feature we did not know we needed. Peliqan builds the lineage for your tables and queries on its own, so you can open a table, go to Details, and see both where the data came from and what is sitting downstream of it.

We found out the hard way. Someone was about to drop a column from a query that half a dozen things depended on, and the lineage view showed exactly what would have broken before we ran it. Previously that was tribal knowledge, and the answer was usually to change it and see who complains.

You can also annotate your own Python scripts so they show up as nodes in the graph, which means the custom steps appear rather than leaving gaps in the chain. Review collected by and hosted on G2.com.

It is a little tucked away. You reach it through Details on a table, and we had been using the platform a while before we realised it was there. Worth pointing out to new users on day one. Review collected by and hosted on G2.com.

We needed a small internal tool for our ops team. Normally that means asking a developer for a form, a backend and somewhere to host it, and then it sits in the queue for a month. We built it as a data app inside Peliqan instead.

It reads live data from our connected sources, shows it in a table the team can filter, and has a few input fields so they can correct a wrong value and have it written back to the source system. They open a link, they see their data, they fix it. No SQL, no exports, no coming to us.

We have built two more since for other teams, and each took an afternoon rather than a sprint because the connectors and the warehouse were already sitting there. The second one we mostly copied from the first. Review collected by and hosted on G2.com.

The one thing we would say is that you want someone comfortable with Python to build the first app. Once one person has done it the pattern is easy to reuse, and there are templates to start from, so it did not hold us up for long. Review collected by and hosted on G2.com.

We already had a Snowflake data warehouse and didn't want a second one. In Peliqan we added Snowflake as a connection and set it as the target, and now our pipelines from HubSpot, Stripe and Xero load into it. Our analysts kept working in the same place. Review collected by and hosted on G2.com.

Small one. When you add Snowflake you need to fill in the target database name so it's set up as your data warehouse. We skipped past that field the first time. Review collected by and hosted on G2.com.

I like how Peliqan sends an event when a pipeline run starts, completes, or fails, which helps our platform start its job when the pipeline run is completed. The ability to run jobs after data sync instead of relying on a fixed timer is really useful. The support team is very helpful whenever we face any issues. Setting up Peliqan was pretty easy, and importantly, our requirements are met with the software. I use it with my analytics software, and it's seamless. Review collected by and hosted on G2.com.

I think it would be beneficial if Peliqan also handled failed and timeout events, as well as completed ones. This way, we can prevent any delays in our workflow when something downstream is waiting on a run that didn't finish. Review collected by and hosted on G2.com.

We do data work for several clients and needed a consistent way to give each one an Al agent over their own systems without running a different tool per client. With Peliqan we connect a client's sources, decide what the agent can read and write, and hand them access through whatever Al client they prefer. One client runs on Exact Online, another on Odoo, and the setup process is the same for both. Keeping each client's environment separate while reusing the same approach is what makes it work for us at the scale we operate. Review collected by and hosted on G2.com.

Hard to fault it for what we use it for. There's clearly a lot more in the platform than the client setups we run day to day, so we may have notes once we go deeper, but so far it's held up. Review collected by and hosted on G2.com.