The trial provides 14 days of access without requiring a credit card. The signup screen shows the included team size and features before you create the account.
Direct answers.Clear boundaries.
Trial, billing, access, files, security, deployment and support without sales language hiding the detail.
The account is paused until a subscription is activated. Your project data is not presented as deleted at the end of the trial. Contact support before the trial ends if you need help choosing a plan.
Yes. Review the effective date shown in the billing flow before confirming. Access normally follows the billing period already paid.
Plan changes are handled through billing. The interface should show the effective date and any amount due before you confirm the change.
Refund eligibility depends on the applicable terms and billing arrangement. Contact billing@meshworks.pt with the account and invoice details for a review.
Online subscriptions use Stripe for supported credit and debit cards. Enterprise billing and bank transfer arrangements are agreed directly with the customer.
Card entry and payment processing are handled by Stripe. MeshWorks uses the resulting billing records and does not need to expose full card details to the application.
Invoice availability depends on the billing arrangement. Check the billing area first, then contact billing@meshworks.pt if a document is missing or requires company details.
The current pricing page shows a 15 percent discount where annual billing is available. Confirm the displayed total before subscribing.
Solo includes 1 user, Startup 5 users, Growth 15 users, and Enterprise is quoted around the required team size.
Use the Customer Portal for controlled external access. Internal organisation membership should be reserved for people who work inside the operating team.
Organisation administrators assign role based access. Server policies enforce the organisation and permission boundary even if someone attempts to bypass the interface.
Their active access is removed. Historical records should keep their original attribution so project and audit history remains understandable.
MeshWorks supports Excel and CSV based BOM imports. Column mapping connects the source fields to the project record.
Neutral Excel and CSV imports remain available. A SOLIDWORKS add in is in development and an Inventor connection is planned behind the same controlled import boundary.
The web application supports modern mobile browsers. Production and QR workflows are the main mobile use cases. There is no separate native application required.
Available settings include branding, quote templates, role views, classification rules, material records and notifications. Some options depend on the selected plan.
Yes. Integrations use authenticated and permission scoped endpoints. The available API and agent capabilities depend on the plan and deployment boundary.
Database row policies and server side authorization scope records to the active organisation and user role. The boundary does not rely only on hidden buttons in the browser.
The managed service uses the configured cloud region. A customer managed deployment keeps the agreed application and data footprint on infrastructure controlled by that customer.
Access follows the deployment and support boundary. In a fully offline customer managed deployment, MeshWorks has no connection to the customer data. Managed support access must be authorized and limited to the work required.
Export options are available across BOM, quote and reporting workflows. The exact formats depend on the module and plan. Confirm any required full export before selecting a deployment.
Export any records your organisation must retain and review the current service terms. Ask support to confirm the applicable retention window instead of assuming a fixed period.
Use support@meshworks.pt or the live chat on the website. For billing questions use billing@meshworks.pt.
Standard support is handled during normal operating hours. A guaranteed response time applies only when it is written into the customer service agreement or SLA.
Documentation and email support are available to every customer. Guided onboarding and implementation support depend on the plan and deployment.
Use a current version of Chrome, Edge, Firefox or Safari. Older browsers without current security and JavaScript support are not targeted.
Cloud customers use a browser. Customer managed deployments require an agreed server, database, identity and update configuration.
New uploads may be blocked until storage is cleared or the plan is changed. Existing project records should not be removed automatically to create space.
Yes. MeshWorks can review part identity, revision rules, ownership and handoffs before automation is introduced. Contact us with a representative BOM and the current workflow.
Talk to the team handling the product.
Send the workflow, deployment question or billing reference and we will route it correctly.