app architecture - multiple sqlite instances running on one server?

I have a web project in which I have about thousand "profiles" to serve up.

I this a reasonable approach:

• each "profile" has its own directory based on an id
• each "profile" directory has an sqlite.db
• user logs in with id, we find the directory and display the data

Notes:

• This is not a public facing site
• For the most part the db calls a just reads by one or two users per "profile"
• These "profiles" are seasonal so they're time sensitive (maintenance will involve deleting directories)

Looking for downsides