
Overview
The Juniper Session Smart™ Networking Platform accelerates and improves the digital transformation journey. Using the innovation from AWS and session-based, service-centric routing from Juniper simplifies the use of AWS Services, streamlines deployments, and brings unprecedented benefits to end users.
With the Session Smart Networking Platform, enterprises can optimize the AWS Services experience, simplifying deployments, delivering zero trust security, providing rich visibility and insights, and offering breakthrough economics with a tunnel-less architecture.
The Juniper Session Smart™ Conductor is a centralized management platform for distributed Juniper Session Smart™ Routers and provides management, control, visibility, and zero-touch provisioning.
The Juniper Session Smart™ Router combines a service-centric control plane and a session-aware data plane and offers simple deployment, security policy enforcement, and multi-path resilience.
The pricing model of this offering is Pay-As-You-Go (PAYG). It provides a free trial period of 30 days and an hourly software cost after the trial expires. This plan is recommended for proof of concepts and trials only. Software upgrades and deployments outside of the cloud, (on-premises) require a token or certificate. The software can not be purchased via the marketplace.
For Private Offers or BYOL, contact your Juniper representative or email Juniper Marketplace Team (JNPR_MP_Team@juniper.net )
Highlights
- Service-centric, multi-path routing delivering SD-WAN, session-resilience, dynamic load balancing, and WAN optimization.
- Zero-trust security with hypersegmentation, session directionality, encryption, and session-stateful firewall functionality.
- Single pane-of-glass management across heterogeneous branch, public, private, and hybrid cloud deployments.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
|---|---|
c5.xlarge Recommended | $0.75 |
c5.18xlarge | $6.44 |
c5n.4xlarge | $2.68 |
c5n.2xlarge | $1.20 |
c6i.8xlarge | $3.10 |
c6i.large | $0.47 |
c6i.16xlarge | $5.60 |
c5.9xlarge | $4.02 |
c5n.9xlarge | $4.02 |
c5n.large | $0.47 |
Vendor refund policy
We do not currently support refunds, but you can cancel at any time.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Additional details
Usage instructions
Once the deployment is completed, SSH to the instance with the following command (note the username is t128): "ssh -i <path_to_key_pair.pem> t128@<instance_hostname>" The deployment can be performed manually or using the associated templates. For additional information, please refer to our documentation site at https://docs.128technology.com/docs/intro_installation_quickstart_aws , or visit the Interchange Community at https://community.juniper.net .
Support
Vendor support
Juniper Networks Technical Assistance Center (JTAC) is your focal point of contact for post sales technical and network-related questions and issues on Juniper products 24x7x365. Please visit the following Juniper Knowledge Base article to obtain support from Juniper Networks: https://kb.juniper.net/KB31158 . Additional information can be found in the JTAC User Guide: https://www.juniper.net/customers/support/ http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf Juniper Networks Technical Assistance Center (JTAC) Website: https://support.juniper.net | Interchange Community:
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.


Standard contract
Customer reviews
Session-based routing has transformed branch failover and now optimizes application paths
What is our primary use case?
My main use case for Juniper Session Smart Router in the lab environment where I've tried learning about Juniper networks is basically SD-WAN and application-aware routing for enterprise WAN transformation.
A realistic example regarding my main use case for Juniper Session Smart Router is a branch failover that previously took manual intervention; now it automatically reroutes traffic based on application SLA degradation.
What is most valuable?
Juniper Session Smart Router is a very good cloud integration router, with very strong application visibility, and WAN path optimization is also present. It has very good simplified branch connectivity, particularly strong automation and API support, and better SaaS performance. Session-based routing instead of tunnel-heavy architecture is one of the best features.
Session-based routing and API support in Juniper Session Smart Router have helped me in my work. It helps in session-based routing changes from route-based packets only on destination IP to application session awareness. This can help with a better application experience, and voice or video traffic automatically takes the best WAN path based on latency, jitter, and packet loss. Faster failover occurs; instead of waiting for routing protocol convergence, sessions can dynamically move to healthier links. Additionally, there is improved SaaS performance. In terms of APIs, I have had a very good experience integrating it with automation platforms like Terraform and Ansible . It has reduced manual errors, and my team has been using the API to automate deployment and dozens of other tasks with branch SSR devices.
Another feature I can think of regarding Juniper Session Smart Router is that there is no traditional overlay tunnel overhead in many scenarios, which is one of the best features. Dynamic path selection based on latency and jitter makes this one of the standout features.
What needs improvement?
Juniper Session Smart Router can be improved by simplifying onboarding for traditional network teams and providing better documentation for complex deployments, as well as improving the GUI for operational workflows and better migration tooling. Having cloud deployment templates would also be a great simplification.
More intuitive troubleshooting visibility would help enhance the experience with Juniper Session Smart Router. Additionally, reducing the learning curve for policy modeling and strengthening third-party ecosystem integrations would be valuable.
For how long have I used the solution?
I have been using Juniper Session Smart Router for approximately 1.5 to 2 years.
What do I think about the stability of the solution?
Juniper Session Smart Router is overall very stable in enterprise deployments. Once properly designed and deployed, it provides good resilience and reliable WAN performance. I can expect a good session-based architecture, dynamic failover, and application-aware routing, and it is generally praised for its stability.
Juniper SSR is generally very stable and is very keen on maintaining its urgent patches.
What do I think about the scalability of the solution?
Juniper Session Smart Router is very scalable for multi-branch enterprises and cloud-first WAN architectures, with its main strength being centralized policy management.
How are customer service and support?
Juniper enterprise support is generally very strong, providing good TAC quality, strong SD-WAN specialists, and a good documentation and training ecosystem. The resolution speed may vary depending on the complexity of the issue, but the support quality is strong technically.
What was our ROI?
I have seen a return on investment; faster incident resolution is something I have observed in terms of realistic metrics for WAN analytics and improved user experience for voice or video apps. Additionally, there was a significant reduction in MPLS dependency.
I can share specific numbers; we achieved a 30 to 60% WAN cost reduction by reducing MPLS usage. The mean time to identify WAN issues was reduced due to application-aware visibility and path analytics.
What's my experience with pricing, setup cost, and licensing?
Pricing for Juniper Session Smart Router is premium but is usually justified for enterprises needing advanced WAN optimization and application-aware routing. Some challenges arise from initial licensing costs feeling very high, and it requires skilled development teams to realize the full value of the product.
Which other solutions did I evaluate?
I evaluated other options before choosing Juniper Session Smart Router. I specifically tried to evaluate Cisco SD-WAN and Fortinet Secure SD-WAN for session-based routing improvement, as they were the most common alternatives available.
What other advice do I have?
Juniper Session Smart Router is rated 8 out of 10 based on my experience with the product.
I rate it an 8 out of 10 because the policy design complexity initially is not great and some of it requires a mindset shift from traditional routing concepts. Additionally, it is a smaller ecosystem compared to Cisco, Meraki, or Fortinet.
My advice for others looking into using Juniper Session Smart Router is to build strong observability first, understand cloud connectivity, and train operations teams early.
Juniper Session Smart Router is a great tool for practicing observability integration and other aspects moving towards SD-WAN and cloud networking, all relating to intent-based network operations. It is a great tool to understand cloud connectivity requirements beforehand.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Session-based routing has reduced WAN costs and delivers faster failovers with app-aware paths
What is our primary use case?
I use Juniper Session Smart Router to connect branch offices to cloud apps like AWS where the router dynamically selects the best path such as MPLS, broadband, or LTE connections based on application performance, ensuring low latency for critical services while enforcing zero-trust security policies.
A key addition to this use case is that because it is session-based rather than tunnel-based, we do not rely on traditional VPN tunnels, which means it has the fastest failovers and better visibility into each application session, along with built-in zero-trust segmentation.
What is most valuable?
The best features of Juniper Session Smart Router that offer me value are the ones I use daily, including session-based routing and core features that route traffic per session instead of tunnels, giving better performance, seamless failovers, and application-aware path selection. It selects the best link, whether MPLS, broadband, or LTE. It also has built-in zero-trust security which means it controls segmentation without needing a separate VPN setup and advanced visibility and analysis, providing strong insight into traffic, session, and performance. This provides simple branch management.
Juniper Session Smart Router has positively impacted my organization by achieving a 30% to 40% reduction in WAN cost, which means less reliance on MPLS. There is also a 40% faster failover with near-zero user impact during link issues, and 20% to 30% less time spent on troubleshooting. Additionally, I experience fewer outages due to dynamic path selection, which facilitates fast branch deployment.
What needs improvement?
Juniper Session Smart Router could be better in several areas such as the steep learning curve because the session-based model is different from traditional networking. The UI could also be more functional and intuitive for day-to-day operations. Troubleshooting can be complex because of the deeper session level, and there is a documentation gap in some advanced sessions and a smaller community ecosystem compared to other SD-WAN vendors.
For how long have I used the solution?
I have been working with Juniper Session Smart Router for almost 14 years.
What other advice do I have?
My advice for someone considering Juniper Session Smart Router is to invest in learning early and understand the session-based routing because it is different from traditional WAN. I also recommend starting with a pilot test with a few branches before full rollout and defining the application policy early and clearly. The biggest value comes from the app-aware routing, so leverage automation because it saves time and scales. Additionally, train your team to reduce troubleshooting friction later. I would rate this solution an 8.5 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Centralized monitoring has improved configuration control but hardware still needs reliability gains
What is our primary use case?
The typical use case is to manage the data center fabric.
What is most valuable?
The best feature is the easiest way to deploy configuration and also back up them, and also to roll back quickly if there's an incident.
We have a better view with all this complexity because we have some probes that monitor the response time, and we can see quickly if there's an integration and so on.
We have many controllers, so we deploy a controller by pods. So we have a nice view, and we're thinking about collecting everything in one controller, but we didn't decide that yet.
We have NetFlow included.
What needs improvement?
They have some improvement to do, so I would say seven.
I found some weaknesses on their hardware. They are sometimes breaking very often.
For how long have I used the solution?
I would say about seven years in total.
What do I think about the stability of the solution?
In general, they are robust and reliable, so I would say eight is a good mark.
How are customer service and support?
Customer service rating: 4
Which solution did I use previously and why did I switch?
From a different vendor.
How was the initial setup?
It was quite straightforward.
What about the implementation team?
I did the architecture and the deployment.
What other advice do I have?
Juniper Session Smart Router is a controller for managing devices. We have real-time analytics through the IBA Probes. For troubleshooting, we have direct access to them. As we use other vendors, we are running also the SASE with another provider. We have the response time, also latency and so on. There are other considerations, but I didn't think about everything right now. My overall rating for this product is 7.
Real-time visibility has strengthened network control and supports long-term enterprise use
What is our primary use case?
I have not tested Sophos on a larger scale, as I use Sophos in a very office environment and Juniper in telecom.
Because we have Juniper switches and Juniper firewalls, we have not centralized them really. I do not prefer centralizing things, as I feel that if someone gains access, they have so much information about my network. This is a personal feeling rather than a professional one.
What is most valuable?
I do use its real-time analytics and visibility features, but I still prefer Sophos to that.
Real-time notifications are where Sophos beats Juniper.
For telecom companies, I think zero-trust segmentation is the way to go because if you allow anything that you do not understand, then it becomes a problem. I am all for zero-trust.
What needs improvement?
Juniper Session Smart Router could improve its documentation to become more competitive.
It has very little documentation, and you have to rely mainly so much on support to do something, which I feel should not be that way. Otherwise, functionality-wise, I feel it is perfect.
It is way high and expensive; that is why most of my clients on the lower end, I cannot suggest Juniper. It is too pricey.
Of late, I am seeing them changing the interface; the UI is changing, and that is a good thing. But still, I feel you can standardize the syntax to be in line with the rest of them.
For how long have I used the solution?
I have been using Juniper Session Smart Router for seven years.
What do I think about the scalability of the solution?
It is scalable, but it is scaling upwards. The only reason I say enterprise is because those people usually have the budget for it, and because it is what I have used in large enterprises, it is what I usually fall back to.
How are customer service and support?
It is good and perfect, but I do not prefer relying on support. I prefer knowing that they are available rather than having to contact them to fix things for me.
How was the initial setup?
Juniper Session Smart Router is not easy to implement; its syntax is totally different, and it is not very easy to implement. If I had to implement things, I would choose Sophos over anything.
Delivered tailored features and meets requirements effectively
What is our primary use case?
We are using it as a DNG. This means all subscriber PPPoE sessions or ILS Smart VPN connections are terminated through the access network to this BNG, Uniphore BNG. From there, they are managed.
What is most valuable?
Everything has been fine. Although we did not explore much about the solution, they provided us with a customized product according to our requirements. It was very well executed.
What needs improvement?
I did not find any problem with Juniper. Regarding improvement, we still need to see what it can do.
For how long have I used the solution?
I have used Juniper for around five years.
What do I think about the scalability of the solution?
We have a limited edition, so we did not use much of the resource capacity. We have our licenses only for the limited edition, and we did not address that yet. As and when licenses are included, we think it will improve scalability.
How are customer service and support?
Customer service is very prompt.
How was the initial setup?
The installation took around three days. I managed the deployment, and the delay was only due to physical arrangements.
What about the implementation team?
Each installation per area or per field or per session involves around two people.
What other advice do I have?
On a scale of one to ten, I rate the solution nine.