Shelf – open-source asset management software(github.com) |
Shelf – open-source asset management software(github.com) |
I have used it for years both self hosted and with them hosting and it's been a great low cost solution for asset management.
https://devboard.gitsense.com/snipe/snipe-it
Full disclosure: The insights are from my tool.
AM to me is the foundational part of any security management. I care about 3 main things:
1) API support (for custom tooling)
2) Integration with other tools (Jira, Salesforce, etc)
3) Relationships/Dependencies with other assets (to determine the blast radius if there is an incident, or if this asset can be deco'd and what the impact would be)
The feature set looks like it steps into EDM, which is a totally different problem space to AM IMO.
What does that mean?
However, the best definitions typically come from NIST which, as a non-US resident, I still recognise are leaders in this space.
Having worked in asset management at one time, the field has some quite difficult aspects that are often missed by these relatively simple systems.
I am not disparaging what either of these systems do. There is a lot of time and effort that has been put into them. However, full blown asset management is a much bigger area than most people understand or have built systems for.
One asset class that can act as a test case for any asset management system that you might like to try your hand at building is a multi-story multi-use building. Once you get into the weeds on this one, you begin to see just how complex asset management is.
One feature of asset management is the oft forgotten maintenance sequences and forecasting of maintenance and refurbishment.
A number of other comments here have commented on such aspects
1. Separates, but inter-connect the Asssets and CI. An asset will never change during its lifecycle. A CI is the actual configuration(s) of an asset. It could be a simple laptop (asset) with a standard OS (CI, one-to-one relationship), or it could be a server (asset) with multiple virtual machines (CI, one-to-many relationship)
2. Will handle the entire lifecycle of the equipment.
3. Will be an integral part of the purchasing, receiving and decommission process.
4. Will allow you to predict and plan the replacement of old assets with a high level of confidence.
The product presented by OP only touches a sliver of what asset management is. For some it might be just enough, but most don't realize how complex it can become.
I'm aware of Snipe-IT, but could you recommend any other open-source solutions?
I have a hunch that the scope and requirements of such software are often tailored exclusively to enterprises, which only comes with a price tag.
I suppose that means this tool is "stable enough for most non-enterprise use-cases", which means I can't use it despite wanting to.
Basically - if you would run it on RDS, you can run it on Supabase
It can be rather tedious to configure, as I recall, but it can do almost whatever you want. Hope you know some perl. Have not used it in at least 5 years.
One thing I couldn't figure out from the website/GitHub - can I attach more than one image to the item? For example I'd like to save both the photo and the pdf of the invoice.
There is very little software like that. Everything is a website or a smartphone app. I want a Windows desktop program.
It can even do things like defining projects that are made of sub-components that are made of parts you may or may not have on stock (and if you added a prize for each of the parts it will spit out a total cost). It can handle prize brackets etc.
For a most basic system or hobbyist needs this might be total overkill tho.
Why not start an excel sheet with everything you have and put an location next to the thing? The major work with such systems tends to be first entry and then keeping things up to date, so starting on a small subset of things and trying it out would be a wise way to go about it.
The page on the forum wiki is https://www.mikrocontroller.net/articles/Elektronik_Lagerver... [] and it speaks mostly about EleLa.
[*] these links are in German.
EleLa is a desktop app for Windows and Linux written in FreePascal with Lazarus PartDB isa PHP server for self hosting
If Docker is an option and you only need it for a single machine, maybe NocoDB?
And infrastructure as code
* No basic fields like a serial number, model, etc * You can't change the color of a category once created * It lacks the ability to make assets templates * No obvious ways to create custom fields
License MIT <3
Look for screenshot
Don't find
Close tab
One downside: the blog entries look like it was written by ChatGPT or similar.
edit: oh its only on the website
At the end of the day I abandoned it but the tech stack and the hardware I bought (small Dymo label printer) actually led to me building a side business on top of some of the basic ideas behind it which has grown steadily since.
I once, many moons ago, barcode asset tagged all my stuff and was scanning it into an app that could track where it was in your house on a basic 2d wireframe home, which let you report for insurance scheduling purposes. Besides just tracking generally, knowing what stuff you have that is valuable, depreciable, and could be stolen/destroyed is very useful data even for individuals.
I was thinking about building myself a system of QR labelled ziplock bags (inc. antistatic ones) and QR labelled containers.
The main concept of my particular system would be to have a camera covering my workspace, and a camera covering a storage area for containers.
The system would automatically track which QR labelled bags are in which QR labelled container, and also keep a 'last seen' graph of bags that are near other bags, and containers near other containers, so that you don't have to spend too much effort maintaining the system, and when you want a list of things to work with, the system could help you perform a 'computer enhanced rummage' by using your smartphone and have it highlight containers that you want, and ziplocks that contain the things on your list.
Take all those ziplocks out, lay them on your workspace, boom, they are all checked out of the containers by the overhead camera.
Place the containers back on your shelves, boom, the shelve cameras know the positions of the boxes.
When you are done with the items, place a box on your workspace (recognised by camera) and put the packets back in the one box (those packets then checked in to that box).
I don't have a nice workspace to build the system yet, but when I settle into a place I am going to spend more time thinking about it.
This is what you're looking for.
In our assessment we found that these APPKEYs are also included in the backup file - which makes the SnipeIT backup ZIP files a vector for exposing all users and passwords (as well as all encrypted fields data) because of a default setting by the framework's backup provider.
That said - if you are concerned about security, you will be on-prem or within your own cloud provider to begin with. The SnipeApp company offers an "enterprise" level support at a somewhat reasonable rate for big companies, and they were a great help assisting with our installation and integrating the SnipeIT API to import new devices and licenses automatically in a way that we can control from say a PO.
This password issue may not be a problem for you as I understand they now have connectors for SSO or another OAUTH provider. That and the fact that they asked us to share our backup via email during onboarding and they did not specify to keep the secrets out of the backup made our decision to go in-house. Still a good, scrappy product, and when we asked them if they had access to our company's passwords that was not disclosed, we didn't get a response. That's OK - and it was a good lesson for my team in evaluating an open source framework behind the product vis-a-vis "trust but verify."
Its always going to be a vector of our own partial design (and/or someone we are paying), a rogue backup source of truth that is ejected into the ether like atoms forming salts in an acid-base reaction.