NeetoDeploy

Platform-as-a-service solution for deploying your applications on the cloud with minimum friction. Alternative of Heroku & render. @NeetoHQ product.

[NeetoDeploy @NeetoDeploy]

🚀 September Updates at NeetoDeploy:

🔹Smarter autoscaling for background jobs
🔹Revamped metrics for Postgres, Redis, & Elasticsearch
🔹DataDog tracing integration
🔹Proactive alerts & more!

https://t.co/yDD6rB1Cjz

#DevOps #Cloud #Monitoring #Scaling

[NeetoDeploy @NeetoDeploy]

NeetoDeploy August ’25 Updates:
• Revamped + Scheduled Autoscaling
• AI-generated build summaries
• Email alerts for high resource usage
• Improved app + addon metrics

https://t.co/IXPtaS6kvT

#DevOps #PlatformEngineering #ProductUpdate

[NeetoDeploy @NeetoDeploy]

NeetoDeploy M39 updates:

✅ New onboarding flow for faster deploys
✅ Native support for pnpm
✅ Procfile buildpack rewritten
✅ Kpack → Pack CLI migration
✅ Grafana storage alerts & more!

Read more: https://t.co/7Jc7Inv4Oh

#DevOps #Rails #NextJS #SaaS #Buildpacks

[NeetoDeploy @NeetoDeploy]

NeetoDeploy M38 milestone updates are here!

✅ SQLite & PostgreSQL 16 support
⚙️ Build system enhancements (Kpack → Pack)
💰 Smarter billing engine
🚧 Onboarding revamp in progress

Checkout the blog: https://t.co/XVrJRSOFgg

#HerokuAlternative #DevOps #CloudDeploy #SaaS

[NeetoDeploy @NeetoDeploy]

We’ve switched our logging system from Loki to CloudWatch! This change reduces server load and boosts scalability. Both app and build logs are now powered by CloudWatch.

[NeetoDeploy @NeetoDeploy]

Take a look at the latest updates and improvements.
Milestone M33 (March 24-April 06) is here! 🎯
https://t.co/g6ooaLzqsN

[NeetoDeploy @NeetoDeploy]

🚨 New Feature Alert!

You now have full control over your Maintenance Mode page on NeetoDeploy! 🎯

Switch between default & custom modes, and design your message for users when your app is down. Watch how it works. 👇

🎥 https://t.co/XSLYEymqIK

#kubernetes #neeto #neetodeploy

[NeetoDeploy @NeetoDeploy]

Take a look at the latest updates and improvements.
Milestone M32 (March 10-March 23) is here! 🎯
https://t.co/QwLe3lUA4J

[NeetoDeploy @NeetoDeploy]

Take a look at the latest updates and improvements.
Milestone M30 (Feb 24 - March-09) is here!

https://t.co/THIQmWLHsU

[NeetoDeploy @NeetoDeploy]

Take a look at the latest updates and improvements.
Milestone M30 (Feb 10 - Feb 23) is here!
https://t.co/WAUkHG7Hcf

[NeetoDeploy @NeetoDeploy]

3. All application dynos run on a private subnet (for security). They pull their OCI images from ECR via the NAT gateway. A private link (VPC endpoint for ECR) was also set up for the private subnet.

[NeetoDeploy @NeetoDeploy]

NAT gateway usage was one of the significant components of our daily AWS cost. We dropped it from 40$ a day to 2.5$.

[NeetoDeploy @NeetoDeploy]

2. A VPC endpoint (AWS Private link) was added for ECR, which enabled traffic to be routed through the AWS internal network instead of through the Internet via the NAT gateway. This also improved performance.

[NeetoDeploy @NeetoDeploy]

Here is the video about how to configure launch layers
https://t.co/JWAmBmZqcN

[NeetoDeploy @NeetoDeploy]

Buildpacks do not run as the root user, meaning buildpack cannot do certain things requiring root permissions. In this case, we can use image extension to make the changes.

[NeetoDeploy @NeetoDeploy]

What is an image extension?

Image extension is software that generates Dockerfiles that can be used to extend the base image for the build process.

[NeetoDeploy @NeetoDeploy]

Check the video to see how we can use the cache layers in the build
https://t.co/vtYE27wyEW

[NeetoDeploy @NeetoDeploy]

Let's see how build layers are configured during the build

https://t.co/wPBYL5KRrW

[NeetoDeploy @NeetoDeploy]

For example, nodejs buildpack creates a layer CNB_LAYERS_DIR/nodejs and defines types in CNB_LAYERS_DIR/nodejs.toml

// CNB_LAYERS_DIR/nodejs.toml file
[types]
build = true
cache = true
launch = true

[NeetoDeploy @NeetoDeploy]

A Buildpack may create different layers(<layer>) inside the CNB_LAYERS_DIR directory. <layer> is a directory where all the packages and dependencies installed by the Buildpack are present.

[NeetoDeploy @NeetoDeploy]

After creating the <layer>, Buildpack defines how the layer should be used.
This is done by creating <layer.toml> file inside CNB_LAYERS_DIR folder and setting build, launch, and cache types.