diff --git a/devdocs/todo.txt b/devdocs/todo.txt
index 98b13e77..090a16db 100644
--- a/devdocs/todo.txt
+++ b/devdocs/todo.txt
@@ -81,28 +81,3 @@ TODO: API docs, make separate page for datalists and remove from api-response-fo
 -------------------------------
 ### LATER (TURN INTO CASES IN ROCKFISH WHERE POSSIBLE AND REMOVE FROM HERE)
 
-todo: hang trial off of App.ayanova.com or make that domain and put a landing page there because it's going to be needed for self host eventually and trials now
-
-todo: some kind of ops specific event log or system that triggers alerts to ops people, I guess notifications would be the word I'm looking for...
-	- Once that exists a lot of backfilling needs to be done for example attachment files missing notification etc etc etc
-todo: Server ops EMAIL address for server to send health messages to!!!!
-	- also maybe whatever other methods people use these days (text?)
-	- Boot config setting
-	- maybe this should be mirrored as a setting in global biz admin as well because the biz admin needs to know about critical server issues or impending doom of the server (disk space etc) just as much as OPS
-		- also OPS people are not always trustworthy
-TODO: API RATE LIMITING / THROTTLING (NOTE: THIS IS MOST IMPORTANT WHEN GET INTO SELF SERVE / HOSTING)
-	- Return code 429 
-	- Going to need rate limiting to save people from themselves 
-	- Have this link from solutions.txt about this: https://github.com/stefanprodan/AspNetCoreRateLimit
-	- All the big api's have hourly limits on requests and also limits on total data throughput per hour 
-	- (minute as well which actually makes more sense since it means they would only be down for a minute if they exceed it) too
-	- Find out what others do
-		- Twitter: https://developer.twitter.com/en/docs/basics/rate-limiting
-		- Zendesk = 100 requests per minute max
-		- https://developer.yammer.com/docs/rest-api-rate-limits
-		- Good developer info here: https://medium.com/clover-platform-blog/conquering-api-rate-limiting-dcac5552714d
-	- Would be nice to have a switch to set for if we host as maximum rates they pay for maybe
-	- On the other hand it's likely a can of worms and maybe it's best they pay for their own hosting and we just set it up or something?
-		- but then it's going to be hard to self serve them where it's all done easy peasy unless we host
-		- Maybe it's a cadillac problem that can wait?
-		- Maybe DigitalOcean has rate limits we can set for the entire server and just mention it as a hard cap to customers
\ No newline at end of file