Questions,
answered.

Both, on purpose. We build and run our own products, Gistly first, and we build software and AI systems for other companies. Each side informs the other: what survives production, and what a business needs from software.

Animastic Inc. is registered in New Mexico, United States, and the team works remotely across time zones. Calls are booked in your time zone and converted to ours; we answer every message within a working day.

Deliberately small: the people who talk to you are the people who build. We bring in specialists when a project needs them, never layers between you and the work.

A call first, then a written assessment of what exists and what it would take, at no charge. Then a contract-first plan with a fixed scope and price, a build with a demo on real data every week, and a handover with the documentation your team runs the system from. Thirty days of post-launch support are part of every engagement.

Almost never. We build on what your team already uses and add a tool only when we can show, in the plan, what it saves and what it costs.

You do. Every engagement ends with the repository, the architecture notes, the decisions we made and why, and a deploy that works from a clean machine. We want your team to be able to run it without us.

The plan states the schedule in weeks, before you commit. Scope is fixed, there is a demo on real data every week, and launch happens when the agreed scope is done rather than when the calendar says.

Yes. Most of our work is remote and asynchronous by design: written decisions, recorded demos, and an overlap of a few hours for calls. Contracts and invoices are in US dollars.

Thirty days of post-launch support are part of every engagement: we watch the system in production and fix what we find. After that you choose: your team runs it from the documentation, or we agree a monthly maintenance scope.

Usually. We start with a review of the code, the infrastructure and the risks, and a written assessment of what we would change and in what order. You decide what to do with it, with or without us.

Gistly, a live-web search and fetch API for AI agents, is public, priced and documented at gistly.si. Relay, Tally, Attend and Keel are in development; each has a page here with what it does and where it stands.

Yes, when they fit, at the public price. A product is never a condition of a project; where ours do not fit, we build with what does.

Gistly has its own documentation, status page and support address at gistly.si; questions about it go there, where the team sees them fastest. The products in development have no support channel yet; write to [email protected] about them, and about the company itself.

AI features we build read only the data a task needs, run in your accounts wherever possible, and never train public models on your information. Where a decision is risky, the system asks a person instead of guessing.

In your own accounts wherever possible: your cloud, your database, your keys. When something must run on our side it is written down in the agreement, with what is stored, where, and for how long.

Yes. An NDA before the first detailed conversation if you want one, and a data-processing agreement wherever we handle personal data on your behalf.

Through your own accounts: named users, least privilege, no shared credentials, and access revoked at handover. We work in your repositories and your cloud wherever possible, and the agreement names every place we do not.

Whichever fits the task and your constraints: hosted or open models, in your region when that matters. We design systems so the model is the easiest part to swap, and we say which one we use and why.

A fixed price agreed after the contract-first plan, with the scope written down. You see the plan and the number before you commit to the build. Gistly is priced per call, and its price list is public.

A fixed price for a fixed scope, paid in milestones that follow the plan: a part at the start, the rest as agreed pieces ship. Changes to the scope are written down and priced before the work, never after.

You do, for what we build for you, once it is paid for. We keep what was ours before the project (our tooling and our products), and we say so in the contract.

Yes. A review, a prototype or one well-chosen feature is a good first project: a small scope, a real result, and a way to see how we work before anything larger.