Which product you need, what a configurator does not do, and what the Logic add-on adds to it. Answers filtered by topic.
Answers to what you ask us most — from which product you need, to what a configurator does not do. Use the filter to narrow the questions down to one topic.
It comes down to where the configuring happens. Web configurators go to your customers and sales people in the browser — they build the product themselves, with no CAD. CAD configurators are a platform for your design office: you set rules over models you already have using Excel-like formulas, and the system generates drawings and manufacturing data from them. Combining them is normal: the web configurator collects the orders, the CAD configurator processes them. On top of either you add add-ons — Logic, when a rule will not fit in a single formula and has to reach into a spreadsheet of yours or a function of your own, and API / ERP, when the values should go straight into your system.
You do. The CAD configurator and Logic both run on your own engineer's machine and work on the files where you keep them — what goes through our server is login, licensing and updates, not your models. The web configurator is a different case: we host it for you, so the published configurator and the orders that come through it sit on our server. Your source CAD never does — what gets published is only what the configurator needs in order to render and to calculate.
Get in touch and we will go through one specific product together — the one that costs your design office the most repeated work. That is the fastest way to see whether a configurator is enough or you need Logic. You then download the CAD configurator and set it up over your own model yourself; for the web configurator we agree on publishing it and connecting your domain.
No. The web configurator runs entirely in the browser over WebGL — the customer rotates the model, changes parameters and sees the result immediately. There is no CAD anywhere in the request path, not even on the server: a server-side CAD could not be licensed for this, would be slow, and could not serve concurrent customers. What the configurator renders from is what you published out of gull system — the fixed geometry, the geometry the inputs drive, the form and the rules.
We host it and connect your own domain to it, so the customer stays on your address and cannot tell the configurator runs on our server. You deal with no server, no certificates, and not with whether it will hold up under a campaign's traffic. You release a new version of the product by publishing it from gull system — it switches over on the site with no change to your pages.
We pass them wherever you want — into a spreadsheet, into a shared folder, or over the API into your own system. The configurator collects the input values the customer set; what happens to them next is your decision, and nothing automated has to follow.
Yes, with the API / ERP integration add-on. The order then travels through no file at all but straight into your system as named values — every input under its own name, not as free text somebody retypes. Without the add-on you still get every order — as a row in Excel or CSV, which every ERP on the market reads. Buy the add-on when that step starts to annoy you, not before.
With the API / ERP integration add-on, yes — the drawing, the DXF and the bill of materials go where they belong with no detour through our servers. The add-on covers both directions, so it is paid for once whether you need incoming orders, outgoing documents, or both. Without it, documents are saved into folders by rules you set yourself.
Yes, and it is a complete option rather than a stepping stone. You build the configurator, publish it to your site, let the orders land in your ERP or a spreadsheet, and a person does the CAD exactly as before. What you gain is a sales tool and an unambiguous, typo-free specification; automatic drawing generation can be added later, or never.
With SOLIDWORKS and Inventor. More will follow — the platform is built so that its core holds no CAD-specific code at all: it evaluates rules and emits neutral commands, which a separate module translates for that particular system. Adding another CAD is therefore a matter of writing one module, not rewriting the core.
No. Rules are written as formulas, the way you write them in Excel — for example D1@Sketch1 = Length + 200. You define the inputs, drag them onto a form, and map them onto the dimensions and features you picked in the model. Anyone comfortable with an IF and a cell reference in Excel is comfortable here.
No, and that is deliberate. Neither the configurator nor Logic draws new geometry — they connect to what you have already built (a finished model, assembly and finished drawing) and drive it. A manufacturing drawing carries dimensions, GD&T, views and notes that are the result of your judgement; generating those automatically would mean guessing. Because the drawing hangs off the same dimensions that change, the CAD keeps it in sync by itself, and the only extra step is exporting the already-current drawing.
PDF from the connected drawing, DXF for cutting, STEP or STL from the geometry, and the drawing's BOM into Excel. You tick what should be exported per document, and in Output documentation you build the folder structure the files land in — including folders named by a formula, so each order creates its own directory.
Three ways. A custom form you assemble yourself and open either in gull system or directly in your CAD's own side panel. An Excel sheet — you point it at a watched workbook and the system processes each new row on its own, unattended. And an ERP interface, which is in preparation. To the platform all three are the same thing: a set of named values.
Two things run on the engineer's machine: the gull system application, and an add-in that loads into your CAD. They talk to each other locally, on that one machine — the engineer clicks a dimension in the model and it appears in the application. Only login, licensing and updates go over the internet.
In where a rule gets its value from, not in what comes out. Neither draws new geometry — both change a model you have already built. The configurator computes with formulas like the ones in Excel, and for most custom work that is enough. With Logic a rule may reach further: look the value up in a table you already keep — an Excel sheet, a CSV, a text file, a parts list — or work it out with a function that will not fit into a single formula. The same holds for the price on a web configurator: without Logic a formula computes it, with them you can take it straight from your own price list.
When a dimension's value cannot be computed from the inputs. Even then the model stays your finished model — what changes is only what governs its dimensions and features. A practical test: can you write the value as an expression over the inputs? If so, a configurator is enough. If you keep it written out in a table, or there is a calculation behind it that does not fit into a single formula, it is a job for Logic.
As software, not as a project. You set Logic up yourself, exactly as you do the configurator — connect to your own model, define the inputs, and say what should govern its dimensions and features. The difference is in how far a rule may reach for its value, not in who writes it.
The CAD configurator is 329 € per month, the web configurator 415 €, and both together 625 €. Setup is 1,049 € once. Paid yearly in advance you pay for 11 months instead of twelve. The full price list including add-ons is public on the Pricing page — nothing waits until a meeting.
Yes — 30 days free, no commitment, full functionality. We do not offer a permanent free tier. If you want to see gull system on your own model sooner than that, send it over and we will go through it together.
The monthly subscription runs month to month and you can end it whenever you want. We keep none of your models, drawings or data — all of it is created on your machines and stays yours afterwards. What stops is generating new variants.