Tileserver capacity is limited.

[blackjack2693]

The tileserver we get the map from is limited in its free capacity, so we need a backup/replacement for a extended deployment. It is especially useful because we are nearing the end of the development process and will not necessarily maintain the program actively.
The alternative should

• comply with the route displayed
• be free to use indefinitely
• limit useless/redundant information, such as names of buildings (they are supplied our application)

The first tileserver we used was a good example of the desired style we are looking for.

[NikkelM]

@blackjack2693 Could you give some more background information on this issue?
The first tilemap we used was one that required an API-Key and was replaced after the monthly limit was used up after ~2 weeks in a month.
The current tilemap is one without an API-Key, so as far as we know, the limit is per-IP, per-day. I know that @PaulVII and @jannikgro once reached the limit, maybe they have more info on this.
Did you reach the limit yourself once or did someone from another team reach out to you? How often approximately did you/they refresh until the limit was reached?
From my personal point of view, this issue is not that important, since a normal user would never refresh the map 500 times per day and exhaust the limit (500 is not the actual value, which I would need to research) as a dev might when testing out features.
We could fall back on the default OSM-Map, which we initially discarded since it includes building-labels which intersects with out own labelling (especially the indoor-Maps as well). If you are of the opinion that unlimited tiles is more important than the visual style, we can change the tilemap.