I've often had the itch to create tooling to automate tasks. Later deciding to make it more generic and open source it. I have such a time trying to give them names. Internal tooling, fine, just name it what it does and move on. Public releases though... Oy, I'm sweating just thinking about it.
While I agree, the name Neo is crap, unfortunately.
It's like how many things are named Fuse or Fusion in open source, or new projects that start up with names that are clearly already dominated by something else. It just doesn't work, doesn't do anyone any good in the long run.
It's worth it to go back to the drawing board for a minute, and just come up with a name. Especially since so much thought and care has gone in to the rest of the app so far. Calling it Neo works like an internal project name, just to fill in the blank and get something started. But as a name that can ship, Neo is never going to work.
Unless it does, and becomes the new defacto Neo. Which could happen. But it's a pipe dream. I think it's better to start off on the right foot with a good name.