G2

Felix E.

Enterprise Java Back‑End Developer

Logistics and Supply Chain

Mid-Market (51-1000 emp.)

10/28/2026

"Knack Centralized Our Logistics Tracking with Strong Permissions and Reporting"

4.5/5

What do you like best about Knack?

Honestly, what I like best about Knack is the way it stitches together all the scattered internal tracking workflows for our logistics backend projects. I’m Felix Eviso, an Enterprise Java Back-End Developer at Apex Logistics Tech, and my plate is constantly full: refactoring legacy Java EE services, troubleshooting web service bugs, configuring application server deployments, and coordinating with our operations and carrier teams. We juggle separate tools for task logs, vendor contracts, exception tracking and database change requests, so flexibility is something I prioritize heavily.

A few months back, we kicked off a legacy backend modernization project with three contracted third-party developers. Before Knack, all their deliverables were stored in cloud folders, shipment exception records sat in spreadsheets, and I relied on separate email threads to follow up on when service patches or API updates would be ready. This constantly created mismatched records and missed handoff deadlines. Now I built linked Knack tables to track project groups, deployment cycles, vendor payment terms and contract expiration dates. Once access is set up, our internal team and contract developers can work inside the same workspace.

Its built-in relational database structure paired with granular user permission settings is where it really shines. I can upload build artifacts, check assigned task groups, log backend change notes, while locking away our sensitive production database details from outside contractors. This level of access control is critical for us.

I also appreciate its reporting features that pull data across all our connected tables. When leadership needs metrics like exception volume per carrier or sprint completion rates for our backend refactors, I can build those views directly inside Knack, no need to export raw data into Excel and manually sort everything. Since we don’t have a dedicated DevOps specialist, its native webhook support cuts down a ton of my manual work.

Knack wasn’t built to replace our core Java backend, and it takes some setup to map all our custom logistics relationships. It cannot handle our high-volume transaction processing or complex Hibernate mappings. Still, it centralizes our vendor records, shipment exceptions, change requests and basic project tracking all in one place. That frees me up to focus on debugging enterprise services, tuning database connection pools, and moving our modernization roadmap forward on schedule. Review collected by and hosted on G2.com.

What do you dislike about Knack?

Honestly, what I dislike most about Knack is its rigid automation limits and shallow API error handling, which create extra troubleshooting overhead while I build internal tracking tools for our logistics backend projects. I’m Felix Eviso, an Enterprise Java Back-End Developer at Apex Logistics Tech, and my schedule stays packed refactoring legacy Java EE services, debugging carrier web service connections, and managing database connection pools. Our small team has no dedicated DevOps specialist, so I rely heavily on tooling that can reliably sync with our Java services without constant babysitting.

A few months back, I built a Knack app to log shipment exceptions and trigger alerts back into our backend. Knack’s webhook payloads lack structured retry logic and clear failure logging. When our Java service briefly throttled API requests during a heavy shipment batch run, Knack just marked the hook as failed without sending detailed response codes. I had to manually cross-reference timestamps from Knack’s sparse event log against our application server logs to figure out which exception records never synced over. This forced me to write a separate reconciliation job in Java to patch missing data, eating up nearly two hours of a sprint day I had reserved for fixing Hibernate mapping bugs.

Its built-in workflow engine also hits hard concurrency caps that catch me off guard. We set up parallel automations to notify dispatch teams, flag overdue vendor deliverables, and sync contract status updates. If four or more automations fire at once, the rest queue up and delay notifications. During our last backend release cycle, delayed alerts meant our operations team only spotted a carrier compliance hold hours after it was logged in Knack. There is no way to prioritize critical workflows inside the builder itself.

I also find its reporting layer clunky for the operational metrics our leadership asks for. While simple table views work fine, it cannot run layered aggregations across linked tables to calculate rolling exception rates or vendor on-time delivery averages. Every time our director asks for this kind of breakdown, I have to export CSV dumps and feed them into our Java analytics script, rather than pulling a live dashboard directly inside Knack.

Knack’s permission model is static too. I can create fixed roles, but I cannot set temporary, time-bound access for short-term contract developers joining a release sprint. I either grant them full vendor access and remember to revoke it manually later, or build duplicate filtered views for every new contractor.

Knack works great for basic relational tracking, but it was never built to integrate tightly with enterprise Java backend pipelines. It cannot handle complex transaction rules or surface granular failure context for API consumers. Even with these drawbacks, we still keep using it for simple internal logging. But these limitations pull my focus away from core engineering priorities: stabilizing our legacy web services, tuning our database connection pools, and staying on track with our long-term backend modernization plan. Review collected by and hosted on G2.com.

What problems is Knack solving and how is that benefiting you?

The main problem Knack solves is the mess of disconnected spreadsheets and disjointed log systems we used to rely on for our internal logistics backend tracking. I’m Felix Eviso, an Enterprise Java Back-End Developer at Apex Logistics Tech, and my workload is always stacked: refactoring legacy Java EE services, debugging carrier web service integrations, tuning database connection pools, and fielding custom tracking requests from our operations team. Since we don’t have a dedicated DevOps engineer, I cannot afford to spend multiple days spinning up throwaway Java CRUD services every time the business needs a new tracker.

A few months ago, our operations team needed a way to record shipment exceptions, track contractor deliverables, and log change requests for our backend modernization work. Before Knack, they kept exception logs in Google Sheets, stored vendor acceptance documents in cloud drives, and sent status updates over email. Data quickly fell out of sync; sometimes I’d receive three separate messages about the same delayed carrier integration, with conflicting timestamps and notes. I built a connected set of tables in Knack to track shipment exception entries, contractor task milestones, vendor payment terms, and contract expiry dates. Once user permissions are configured, our ops team and contracted developers can submit updates, view relevant records, and leave notes all within one shared workspace.

Its relational table structure paired with fine-grained permission controls is where it delivers the biggest value. I can attach build artifacts and service test results to task records, filter views so dispatch staff only see active shipment issues, and restrict outside contractors from viewing sensitive database configuration notes. This layer of access control is essential for us, because we regularly bring on short-term contract developers to help with our backend rewrite.

I also lean heavily on its native webhook functionality. When an operator submits a high-priority shipment exception in Knack, the webhook pushes that record into our Java backend automatically. Before this setup, I maintained a scheduled polling job running every five minutes in our application server to scan spreadsheets for new entries. Removing that recurring background job lightened the load on our already busy app server, which was an unexpected win I had not planned for.

Knack is not built to replace our core Java backend, and complex aggregated reporting or advanced error handling still requires custom code on my end. It cannot process our high-volume shipment transactions or manage our intricate Hibernate entity mappings. Even so, it eliminates the need for me to build trivial internal tools from scratch every time the business has a new tracking requirement. This cuts down hours of repetitive backend boilerplate work each week, freeing me to focus on the work that actually moves our roadmap forward: fixing broken enterprise web services, optimizing database connection pools, and pushing through our legacy application modernization schedule. Review collected by and hosted on G2.com.