Sold by: Polars
Deployed on AWS
Polars Cloud processes your data with a unified API and zero infrastructure management. Run blazingly fast queries at scale in minutes. Start with a free 30-day trial.
Overview
Polars Cloud is built by the organization behind the open source project and brings the blazingly fast performance of the popular DataFrame library (17M+ monthly downloads) to AWS with seamless scaling and zero infrastructure management.
Scale your local Polars queries to large-scale production datasets effortlessly with the familiar Polars API. Run workloads on powerful single instances or scale out with the new distributed engine.
Why Polars Cloud?
Modern machines are more powerful than ever. Most workloads can run fast and efficiently on single machines, eliminating the complexity and cost of distributed solutions. Polars Cloud extends this philosophy from laptops to workloads at scale, making your compute infrastructure more efficient, simple and cost-effective.
Key capabilities:
- Execute batch jobs or run interactive analysis at scale
- Same Polars API across all environments
- Pay only for compute you use
- Seamless scaling from local to production datasets
- Deploy close to your data
Learn more at https://cloud.pola.rs/ or reach us at support@polars.tech
Highlights
- SEAMLESS SCALING: Execute queries on single machines or scale out with our distributed engine. Same Polars API from laptop to large scale production datasets.
- UNIFIED DATAFRAME API: Build ETL pipelines, run interactive analytics, or perform complex analysis with familiar Polars syntax. Write once locally, deploy anywhere.
- ZERO INFRASTRUCTURE MANAGEMENT: Polars Cloud instantly provisions compute resources (CPU or GPU) when needed and shuts them down when complete. Focus on your data, not infrastructure.
Details
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Description | Cost/unit |
|---|---|---|
Polars Compute units | Units used with Polars Cloud | $0.01 |
Dimensions summary
Polars Cloud uses a single usage-based dimension: Polars Compute units. You pay only for compute time your queries actually consume, billed per second. There are no upfront costs, no minimum spend, and no charges when queries are not running. Usage scales up or down with your workload, so your bill tracks the amount of compute you use. Because pricing follows actual query execution, costs grow as you process more data or run larger clusters, and drop to zero when idle. This one metered dimension keeps the pricing structure simple and tied directly to your consumption.
Top-of-mind questions for buyers
A compute unit maps to compute resources measured in vCPU-hours, billed by the second while your query runs. You pay for the processing power used to execute queries. When no query runs, no units accrue, so usage scales down to zero.
You are charged only while queries execute. Idle time and paused work accrue no compute charges. When you scale out to multi-node clusters, you use more vCPU per second, so cost rises with the added cores. Costs drop to zero when nothing runs.
Compute runs in your own cloud environment, close to your data. Running near your data helps you avoid data transfer costs and reduce latency. You pay for the compute time used per second, with no upfront costs and no minimum spend.
cloud.pola.rs
Helpful?
Vendor refund policy
Polars Cloud does not offer refunds.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
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.
Similar products
The Japan Aerospace EXploration Agency (JAXA) SELenological and ENgineering Explorer (SELENE) mission’s Kaguya spacecraft was launched on September 14, 2007 and science operations around the Moon started October 20, 2007. The primary mission in a circular polar orbit 100-km above the surface lasted from October 20, 2007 until October 31, 2008. An extended mission was then conducted in lower orbits (averaging 50km above the surface) from November 1, 2008 until the SELENE mission ended with Kaguya impacting the Moon on June 10, 2009. These data were collected in monoscopic observing mode. To create these analysis ready data, we have taken the JAXA Data ARchives and Transmission System (DARTS) archived data, map projected the data to equirectangular or polar stereographic (pole centered) based on the center latitude of the observation, and converted to a Cloud Optimized GeoTiff (COG) for online streaming. These data use a priori spacecraft ephemerides (for the nominal mission) and im[...]
The Japan Aerospace EXploration Agency (JAXA) SELenological and ENgineering Explorer (SELENE) mission’s Kaguya spacecraft was launched on September 14, 2007 and science operations around the Moon started October 20, 2007. The primary mission in a circular polar orbit 100-km above the surface lasted from October 20, 2007 until October 31, 2008. An extended mission was then conducted in lower orbits (averaging 50km above the surface) from November 1, 2008 until the SELENE mission ended with Kaguya impacting the Moon on June 10, 2009. These data were collected in monoscopic observing mode. To create these analysis ready data, we have taken the JAXA Data ARchives and Transmission System (DARTS) archived data, map projected the data to equirectangular or polar stereographic (pole centered) based on the center latitude of the observation, and converted to a Cloud Optimized GeoTiff (COG) for online streaming. These data use a priori spacecraft ephemerides (for the nominal mission) and im[...]
These data are red and color Reduced Data Record (RDR) observations collected and originally processed by the High Resolution Imaging Science Experiment (HiRISE) team. The mdata are processed from the Planetary Data System (PDS) stored RDRs, map projected, and converted to Cloud Optimized GeoTiffs (COGs) for efficient remote data access. These data are not photogrammetrically controlled and use a priori NAIF SPICE pointing. Therefore, these data will not co-register with controlled data products. Data are released using simple cylindrical (planetocentric positive East, center longitude 0, -180 - 180 longitude domain) or a pole centered polar stereographic projection. Data are projected to the appropriate IAU Well-known Text v2 (WKT2) represented projection.
These data are digital terrain models (DTMs) created by multiple different institutions and released to the Planetary Data System (PDS) by the University of Arizona. The data are processed from the Planetary Data System (PDS) stored JP2 files, map projected, and converted to Cloud Optimized GeoTiffs (COGs) for efficient remote data access. These data are controlled to the Mars Orbiter Laser Altimeter (MOLA). Therefore, they are a proxy for the geodetic coordinate reference frame. These data are not guaranteed to co-register with an uncontrolled products (e.g., the uncontrolled High Resolution Science Imaging Experiment (HiRISE) Reduced Data Record (RDR) data). Data are released using simple cylindrical (planetocentric positive East, center longitude 0, -180 - 180 longitude domain) or a pole centered polar stereographic projection. Data are projected to the appropriate IAU Well-known Text v2 (WKT2) represented projection.
Customer reviews
No customer reviews yet
Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.