Lytho is built to help users communicate on-brand with their DAM Solution. The vendor states that users can streamline marketing efforts and save time creating, searching, sharing and publishing digital content, adding that users can: Be consistent with its Brand Center. Be efficient with its Digital Asset Manager. Be creative with its Create and Publish functionality. Lytho is a single source from which to manage, create and publish all marketing content.
N/A
Perforce P4
Score 7.7 out of 10
N/A
Perforce P4 (formerly Helix Core) is the company's version control and peer code review solution. Perforce offers add-on products for code review for free, and Git support products.
N/A
Pricing
Lytho Digital Asset Management
Perforce P4
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Lytho Digital Asset Management
Perforce P4
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Lytho Digital Asset Management
Perforce P4
Features
Lytho Digital Asset Management
Perforce P4
Version Control Software Features
Comparison of Version Control Software Features features of Product A and Product B
Our creative and marketing department consists of several team members with various roles in the organization and process. We receive creative requests from the program managers and other marketing specialists daily. Lytho helps us keep track of all of these projects while listing due dates, proofing dates, completion dates and has the ability for multiple reviewers to be added to the proofing routes. We're able to customize each proofing route to best suit each client. We also have the ability to add outside clients to the proofing routes, which makes the process much smoother. At times I'd say it is less appropriate for very small requests or projects that did not need to go through a full-blown proofing route.
For large-scale codebases with fixed and regular releases that do not follow a continuous delivery paradigm, Perforce is certainly well suited. In projects that are small and distinctly separated from other discrete (though potentially dependent) units, the benefits of the Perforce tool may not be as clear of a victor over other systems.
We have a need to consolidate into a single package, and have such a large variety of technical proficiency among our users that Perforce seems less suitable. Many would like to remain using it, however, even those who use Perforce are the minority, and are often limited to our development teams.
With Perforce Helix, you can use it via the command line, via P4V, or any of the other APIs included with the product. It is extremely easy for new users to get up and running. Users of Perforce Helix only have to pull in the files of interest to them. Also, Perforce is very easy to script and integrate into your CI/CD pipeline. Streams allows you to have pinpoint control of your workflow, and P4Search is the absolute best--I wish Perforce (the company) would talk more about this. It is absolutely fabulous!
In our large environment, Perforce is rarely "down". We have regular maintenance windows and from time to time Perforce can feel a little slow, but its always available. Tech support has always worked with our engineers and IT department to make sure that any real performance or stability issues are addressed quickly.
I had two representatives from Perforce contact me after downloading it but never responded when I had questions. I also had a difficult time finding good training material for getting started. There is a lot of available support material when running into issues, though, because of how many large companies use it.
This rating is related to setting up an environment from an existing Perforce repository. Initial setup of Perforce as the repository for the company was done by a separate team long prior to my inception.
We currently use Canto for our final art file storage as well as a web dam for our art files, client files, client portals, etc. Canto and Lytho work seamlessly together in my personal opinion. So, the two should not be stacked against each other but moreso working in tandem. Canto does not have the ability to assign projects and/or proofing abilities.
New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that requires hours to pull together that would take me less than 30 seconds in Perforce Helix. Large file storage in Bitbucket is clunky and requires you to jump through too many hoops. It's not even something you have to think about with Perforce Helix, as you are only limited by your OS. Perforce Helix is very easy to use even for non-developers. I wouldn't dare ask a non-developer to store their documentation in Bitbucket.