CheckPoint is a digital access management and engagement system for venues. It automates and digitizes the registration, ticketing, and check-in process while enabling venues, vendors, and exhibitors to engage with guests directly to their phone's lock screen. CheckPoint is an event management tool for events, conferences, festivals, clubs, and more. The venue management solution boasts users among both the Oscars and Nasdaq.
N/A
Dryfta
Score 3.0 out of 10
N/A
Dryfta is and event
platform that is comprised of a free suite of applications that are designed to
collect event data and measure event ROI, sell tickets, build event websites,
launch mobile apps, engage and network attendees, retrieve and manage leads for
exhibitors with a unified CRM, segment attendees and create email campaigns,
create shareable real-time custom reports and more.
CheckPoint performs well as an internal firewall between network zones, providing policy control and deep inspection of internal traffic. It works well for a multi network setup like ours across multiple sites. It is however not a fast changing interface and time needs to be taken to perform changes. It's not a quick as other vendors
I can't provide a scenario where Dryfta could be well suited. I guess it's a matter of delivering what has been promised on time, and without having to invest thousands of hours in extra work, as it was in our case. If it worked properly it could be a good tool for any conference.
It has a lot of functionalities (website and administration) all included in the same platform. If it worked properly, it allows you to organise a conference paper-free.
In my experience, notifications are completely broken and non-functional
In my opinion, confusing UX for the cloud portal
Don't try and import 100's of endpoints when onboarding because it will create a mess
When installing the CP client you have to remove Microsoft Defender and if that fails, CheckPoint technical support goes, "Not my problem, sucks to be you!"
Multilingual issues. Although it is advertised as multilingual, it didn’t really work as such. The many issues that popped up throughout the conference preparation were fixed little by little at a cost in time, from help desk emails and to struggles with the unfriendly UX.
Admin pages reloaded every time you clicked on a button (their developers seem to ignore Ajax technologies). It was time-consuming and required constant page searches.
Inflexibility in many of the supposed functionalities it offers.
Certificates were not modifiable nor custom when we had to send them (it was solved months after the conference finished when we were surprisingly contacted by the help desk).
Problems with the size of images to be displayed on the site, very small fonts and limited options to display content. We had to hire a professional developer in order to get a graphically consistent and presentable website.
Very poor mobile version. Too big margins, unreadable text, endless text blocks and lists, distorted pictures, etc.
Issues with the ordering of the authors’ names for different proposals (authorship being so important in research).
Fixed, inflexible fields in the contact sheets, speakers info, and so on.
Special character issues (due to Latin characters and other types used in linguistic research).
Not being able to include links in the HTML editor due to Dryfta's inadvertent decisions to block them.
Only one Superadmin user allowed to access the full functionalities of the platform, so we had to share it (consequently not knowing who did each action).
Problems with the generation of reports and the high complexity of their interface.
Some issues on the mandatory anonymity. The double-blind review process not fully respected due to unclear user info and options, with other issues coming up on the go such as unwanted info in automated notifications and messages in the Welcome dashboard.
Not being able to use the other payment methods on the platform because they were incompatible with the conference country.
Missing information and time wasted when creating events for sessions with info that already existed in the server that randomly failed to be selected. These issues were reported even with video proofs (help desk didn’t believe us), and were never solved. We had to repeat the same processes again and again, never knowing what was going on
the solution offer the most improvement about the usability by management more firewall in the same context or multicontext instead. The shared database allow to use one object for more than a package target of a cluster or more of gateways firewall. The management remain isolated from traffic pass through the firewall so the disruption is limited at minimum.
It was quick, that's all we can say. Quite a few times they sorted out the problems and issues. But, sadly, sometimes their answers were useless and irritating (not addressing the problem or simply ignoring it, "passing the buck"). In some cases, they pretended the problem didn't exist and we had to send them videos as proof. No response to that.
The CheckPoint Firewall and Cisco ISR router serve different purposes. Our organisation uses both devices, but in different areas of the topology. The Cisco ISR is a remote device and its function is to relay information to our edge firewall, which then passes to our internal firewall (CheckPoint) to securely control traffic requests.
The overall performance was okay in the end, but it was due to our team's commitment and effort. Without that extra work, the results would have been awful.
